Dear m2e community, I'm just using: - Eclipse Juno 4.2 - Eclipse m2e 1.3.1 - Maven 3.xx
having a typical JAX-WS Maven plug-in mentioned in my POM whose default goal "wsimport" by default is assigned to the Maven "generate-sources" lifecycle phase (see: https://repository.sonatype.org/service/local/repositories/central-proxy/archive/org/jvnet/jax-ws-commons/jaxws-maven-plugin/2.2/jaxws-maven-plugin-2.2.jar/!/META-INF/maven/plugin.xml): ... <plugin> <!-- the plug-in can be called via the configured alias "goalPrefix" mentioned in the plugin descriptor of the plugin --> <groupId>org.jvnet.jax-ws-commons</groupId> <artifactId>jaxws-maven-plugin</artifactId> <version>2.2</version> <executions> <execution> <phase>generate-sources</phase> <goals> <goal>wsimport</goal> </goals> </execution> </executions> ... </plugin> ... The problem: although this plug-in is bound to lifecycle phase "generate-sources", it's not taken into account when starting the m2e run task "Maven generate-sources" via: - right-click on Eclipse project - choose "Run as" - select "9 Maven generate-sources" This run is provided by default when installing m2e via the SpringSource tool suite. I only get the following log output: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building FirstSpiritWeb 1.0.0-BUILD-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.142s [INFO] Finished at: Mon Feb 25 19:41:58 CET 2013 [INFO] Final Memory: 1M/15M [INFO] ------------------------------------------------------------------------ When creating a custom run configuration, the plug-in is executed completely successfully. Any idea why that happens and how to solve? Kind regards, Holger _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
