Hi all,
I've used Maven (b7) yesterday for the first time in my life and stumbled
accross the following:
when I issued "maven java:jar", it complained that the Ant's optional
JUnitTask class can't be found.
On a closer look, it's no surprise as the forehead.conf doesn't include
junit-3.7.jar in the [root] classloader. Since Ant code classes are OTOH
loaded from the [root] classloader, the Ant's TaskDefiner can't resolve
JUnitTask's class name using Class.forName().
I placed ${maven.home}/repository/junit/jars/junit-3.7.jar into the [root]
classloader and it solved the problem. Is it OK to do it this way?
My other question concerns the automatic download of dependencies. I was
building Jaxen using Maven, and Jaxen's project.xml declares only a handful
of dependencies. Regardless, issuing "maven java:jar" caused it to download
everything and the kitchen sink from the remote repository, some 18MB of JAR
files in total which was a *bit* painful over my narrowband ISDN line... I
just don't get why did it download i.e. AspectJTools (5 megs alone), batik,
fop, etc. My guess is that it's required to build various site:* tasks, but
I was performing a java:jar task, not any of site:* tasks and didn't expect
it to trigger a monstre download. Is this how it is supposed to work?
Cheers,
Attila.
--
Attila Szegedi
home: http://www.szegedi.org
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
