Jarrell, Maury wrote:
Hi, J.B.,
I had a similar issue when I first tried to get Maven working. In my case, it had to do with Class Loaders and which ones are loading what. What finally fixed it for me was to put the junit-3.8.1.jar in my $MAVEN_HOME/bin/forehead.conf file in the root section like so:
[root] ${tools.jar} ${maven.home}/lib/commons-grant-1.0-beta-4.jar ${maven.home}/lib/ant-1.5.3-1.jar ${maven.home}/lib/endorsed/xml-apis-1.0.b2.jar ${maven.home}/lib/ant-optional-1.5.3-1.jar ${maven.home}/lib/endorsed/xerces-2.4.0.jar ${maven.home}/lib/commons-logging-1.0.3.jar ${maven.home}/lib/log4j-1.2.8.jar /u01/home/oracle/fhrcc/lib/junit-3.8.1.jar
Here's how I solved it...
1. Hunt down multiple copies of clover.jar (v1.2 and v1.2.3). Blow away all but one.
2. maven clean 3. maven test 4. maven site:generate
Problem solved.
Another place I didn't take advantage of in my first few weeks was the
documentation for the plugins. (Again on the maven site under reference and
then plugins. Click on the "Maven Plugins" link under the heading "Plugins
Hosted by Maven" and you'll find tons (pounds?) of good info.)
Excellent, excellent. I shall partake.
Hope this helps,
Oh it /does/, it /does/. You can see the fruit of my labor and your help at diasparsoftware.com/toolkit.
--
J. B. Rainsberger,
Diaspar Software Services
http://www.diasparsoftware.com :: +1 416 791-8603
Let's write software that people understand
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
