plugin seems effectively dead, and particularly because there is no
official support for Java 1.5
Przemyslaw Madzik wrote:
>
> Hello,
>
> I have problem with maven 2.0.6 and xdoclet-maven-plugin (1.0-alpha-2).
>
> After creating simple project (mvn archetype:create
> -Dgrou
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
m
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
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 :
>
>
> xdoclet-maven-plugin
>
maven 2.0.6 and xdoclet-maven-plugin (1.0-alpha-2).
After creating simple project (mvn archetype:create
-DgroupId=com.mycompany.app -DartifactId=my-app)
and adding following section to pom.xml:
org.codehaus.mojo
xdoclet-maven-plugin
1.0-a
Hello,
I have problem with maven 2.0.6 and xdoclet-maven-plugin (1.0-alpha-2).
After creating simple project (mvn archetype:create
-DgroupId=com.mycompany.app -DartifactId=my-app)
and adding following section to pom.xml:
org.codehaus.mojo
xdoclet-maven
