just a random thought: It occured to me that certain goals need certain third libraries or dependencies where as other goals need other dependencies. The test cases need junit (OK in this case the test plugin itself inserts junit into the classpath) and maybe some test base classes from somewhere and xdoclet needs a whole bunch of jars that might even be incompatible with the jars I need to compile my project with. Now if I could restrict for certain dependencies in what goals/plugins they show up the problem would be solved. Something like:
<dependency>
<id>xdoclet</id>
<version>1.2b2</version>
<artifactId>xdoclet-ejb-module</artifactId>
<artifactId>xdoclet-jboss-module</artifactId>
<artifactId>xdoclet-xdoclet-module</artifactId>
<artifactId>xdoclet-web-module</artifactId>
<artifactId>xdoclet-xjavadoc</artifactId>
<artifactId>xdoclet-jmx-module</artifactId>
<artifactId>xdoclet-jdo-module</artifactId>
<property>
<scope>xdocletGoal</scope>
</property>
<url>http://xdoclet.sourceforge.net/</url>
</dependency>
Btw I just thought it would make sense to add more
than one artifactId into a dependency element,
they all share the same id, url and properties.
The maven.dependency.classpath now depends on the context
of the goal it's used.have a nice weekend
Cheers
Justinus
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
