This is completely a "maven" thing and nothing to do with the CXF plugins.
Configuration found in an "execution" is only used when that execution is triggered. That would normally be when the given lifecycle phase is triggered. For example "mvn process-classes". If you invoke a plugin directly like you are doing, only the config outside the executions would be enabled. Dan On Saturday 13 March 2010 7:07:22 am [email protected] wrote: > Hi, > > I have configured the maven cxf-java2ws-plugin as below (cxf version is > 2.2.6) > > <plugin> > <groupId>org.apache.cxf</groupId> > <artifactId>cxf-java2ws-plugin</artifactId> > <version>${cxf.version}</version> > <dependencies> > ..... > </dependencies> > <executions> > <execution> > <id>process-classes</id> > <phase>process-classes</phase> > <configuration> > <className>my.Service</className> > <genWsdl>true</genWsdl> > <verbose>true</verbose> > </configuration> > <goals> > <goal>java2ws</goal> > </goals> > </execution> > </executions> > </plugin> > > and when I invoke > > mvn -Dmaven.test.skip=true cxf-java2ws:java2ws > > I got a build error > > [INFO] One or more required plugin parameters are invalid/missing for > 'cxf-java2ws:java2ws' [0] Inside the definition for plugin > 'cxf-java2ws-plugin' specify the following: <configuration> > ... > <className>VALUE</className> > </configuration>. > > If I move the configuration section as below it works ! So I couldn't > configure more than one service. Any idea's why plugin could not find > className into execution tags as documented everywhere? > > <plugin> > <groupId>org.apache.cxf</groupId> > <artifactId>cxf-java2ws-plugin</artifactId> > <version>${cxf.version}</version> > <dependencies> > ..... > </dependencies> > <executions> > <execution> > <id>process-classes</id> > <phase>process-classes</phase> > <goals> > <goal>java2ws</goal> > </goals> > </execution> > </executions> > <configuration> > <className>my.Service</className> > <genWsdl>true</genWsdl> > <verbose>true</verbose> > </configuration> > </plugin> > > > Thanks for help -- Daniel Kulp [email protected] http://dankulp.com/blog
