Why don't we get a dependency failure if maven cannot built the expected
classpath ?
2007/4/4, Jörg Schaible <[EMAIL PROTECTED]>:
nicolas de loof wrote on Wednesday, April 04, 2007 5:24 PM:
> I got the same issue.
> xdoclet plugin requires some ant classes. Maven 2.0.6 seems
> to make changes
> in plugins classpath and you have to add a dependency to the plugin :
>
> <plugin>
> <artifactId>xdoclet-maven-plugin</artifactId>
> <groupId>org.codehaus.mojo</groupId>
> <executions> <execution>
> <id>xdoclet</id>
> <phase>generate-resources</phase>
> <goals>
> <goal>xdoclet</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <tasks>
> <hibernatedoclet
> destdir="${project.build.outputDirectory}"
> mergeDir="${basedir}/src/main/merge">
> <fileset dir="${basedir}/src/main/java"
> includes="**/domain/*.java" />
> <hibernate version="3.0" />
> </hibernatedoclet>
> </tasks>
> </configuration>
> <dependencies>
> <dependency>
> <groupId>ant</groupId>
> <artifactId>ant</artifactId>
> <version>1.6.5</version>
> </dependency>
> </dependencies>
> </plugin>
However, the origin of this problem is the dependency on the antrun
plugin, that is referenced in the plugin's deps as jar...
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
