Hi,

*I think* the <pluginManagement> section only sets defaults. To
actually bind the plugin to the lifecycle, you need to add something
like this (in parallel of the pluginsManagement element):

<plugins>
  <plugin>
    <artifactId>xdoclet-maven-plugin</artifactId>
    <groupId>org.codehaus.mojo</groupId>
    <version>1.0-alpha-1</version>
  </plugin>
</plugins>

This will tell maven that you want that plugin to be activated, using
the configuration in the pluginsManagement element.

Note: I think the pluginsManagement element is only useful if you have
a parent project, and you want the plugins configuration to propagate
to the child POMs. If you only have one project, you might as well
write it all in a <plugins> element, with no pluginsManagement
element...but wait till someone from the Maven team confirms this.

Cheers,
  Arik.
On 10/12/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> Anybody able to help? I think I did follow the instructions on
> http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html
>
> Thanks!
>
> On 10/11/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I've tried to configure Xdoclet with M2 but it's not calling the xdoclet
> > goal. Here's the configuration I've added to my EJB project's POM:
> >
> >  <build>
> >  <pluginManagement>
> >  <plugins>
> >  <plugin>
> >  <artifactId>xdoclet-maven-plugin</artifactId>
> >  <groupId>org.codehaus.mojo</groupId>
> >  <version>1.0-alpha-1</version>
> >  <executions>
> >  <execution>
> >  <phase>generate-sources</phase>
> >  <goals>
> >  <goal>xdoclet</goal>
> >  </goals>
> >  <configuration>
> >  <tasks>
> >  <ejbdoclet
> >  destdir="${project.build.outputDirectory}">
> >  <fileset
> >  dir="${basedir}/src/main/java" includes="**/*Bean.java" />
> >  <deploymentdescriptor
> >  destDir="${project.build.outputDirectory}/META-INF" />
> >  </ejbdoclet>
> >  </tasks>
> >  </configuration>
> >  </execution>
> >  </executions>
> >  </plugin>
> >  </plugins>
> >  </pluginManagement>
> >  </build>
> >
> > When running m2 install the output is as follows:
> >
> > [INFO]
> > -------------------------------------------------------------------------
> > ---
> > [INFO] Building PRM Core Application Services
> > [INFO] task-segment: [install]
> > [INFO]
> > -------------------------------------------------------------------------
> > ---
> > [INFO] [resources:resources]
> > [INFO] [compiler:compile]
> > [INFO] Nothing to compile - all classes are up to date
> > [INFO] [resources:testResources]
> > [INFO] [compiler:testCompile]
> > [INFO] No sources to compile
> > [INFO] [surefire:test]
> > [INFO] Setting reports dir:
> > C:\dev\projects\PRM\PRM-WORKSHOP\core\business\prm-c
> > ore-business-service\target/surefire-reports
> >
> > -------------------------------------------------------
> >  T E S T S
> > -------------------------------------------------------
> > There are no test to run.
> >
> > Results :
> > [surefire] Tests run: 0, Failures: 0, Errors: 0
> >
> > [INFO] [ejb:ejb]
> > [INFO] Building ejb prm-core-business-service-1.0
> > [INFO] Building jar:
> > C:\dev\projects\PRM\PRM-WORKSHOP\core\business\prm-core-bus
> > iness-service\target\prm-core-business-service-1.0.jar
> > [INFO] [install:install]
> > [INFO] Installing
> > C:\dev\projects\PRM\PRM-WORKSHOP\core\business\prm-core-busine
> > ss-service\target\prm-core-business-service-1.0.jar to C:\Documents and
> > Settings
> >
> > \Thoma.Van-de-velde\.m2\repository\com\whatever\adsj\prm\core\business\service\
> > prm-core-business-service\1.0\prm-core-business-service-1.0.jar
> > [INFO]
> > -------------------------------------------------------------------------
> > ---
> > [INFO] BUILD SUCCESSFUL
> > [INFO]
> > -------------------------------------------------------------------------
> > ---
> > [INFO] Total time: 2 seconds
> > [INFO] Finished at: Tue Oct 11 09:40:58 CEST 2005
> > [INFO] Final Memory: 3M/6M
> > [INFO]
> > -------------------------------------------------------------------------
> > ---
> >
> > I don't see it passing through the generate-sources phase. ??
> >
> > Thanks!
> >
> > Thomas
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to