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
nicolas de loof wrote on Thursday, April 05, 2007 9:20 AM:
Why don't we get a dependency failure if maven cannot built the
expected classpath ?
It can, but with different versions. The xdoclet plugin itself does not declare
any dep to ant, so it is inherited. The problem is, that the used
I got the same issue and raised a jira issue
http://jira.codehaus.org/browse/MNG-2917
But I managed to solve it by re-deploying the maven plugins to our internal
repository with patched poms and different version names. We need to do
this anyway to use the xjavadoc supporting Java 1.5
This
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
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
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
