| Re: [m2e-users] Eclipse standard m2e Maven task "generate-sources" | Custom bound plug-ins (here: "wsimport" of "jax-ws") |
Hi Anders, thanks for the hint. I also reviewed the meaning between “pluginmanagement” and “plugins”. Now, I see the phase “generate-sources” within the lifecycle mapping of the Eclipse project. The element is marked in red color and does not own a mapping. Do I have to map it directly within the POM “pom.xml” or do I have to offer a mapping in: “D:/workspace/.metadata/.plugins/org.eclipse.m2e.core/lifecycle-mapping-metadata.xml” (what seems to be “experimental”) via the following? <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.jvnet.jax-ws-commons</groupId> <artifactId>jaxws-maven-plugin</artifactId> <versionRange>[2.2,)</versionRange> <goals> <goal>wsimport</goal> </goals> </pluginExecutionFilter> <action> <execute /> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> Von: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von Anders Hammar Right, the problem is that you have the jax-ws plugin declared in the pluginManagement section. To get a binding to a phase it should be in build/plugins. /Anders On Thu, Feb 28, 2013 at 9:44 AM, King Holger (CI/AFP2) <Holger.King@xxxxxxxxxxxx> wrote: Hi Anders, when taking a look in the Eclipse-UI in the project properties under “Maven” -> “Lifecyle Mapping” (having checked the “Show lifecycle phases” checkbox and disabled “Show ignored executions”), I see the following content: process-ressources resources:resources execute default compile compiler:compile configurator,configurator extension process-test-resources resources:testResources execute default test-compile compiler:testCompile configurator,configurator extension To my understanding this file shows the mapping between the Eclipse build lifecycle (runtime/incremental) and its bound Maven plugins. Currently, it does not contain the “jax-ws” plugin respectively its goal “wsimport”. Additionally, you get – as you requested the complete Maven POM “pom.xml” file: <?xml version="1.0" encoding="UTF-8"?> <!-- the POM file is the source for Eclipse project configurations. Its values are setting up the Eclipse project, like used JRE/JDK version, project facets, builders, etc. --> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.bosch.bgn</groupId> <artifactId>FirstSpiritWeb</artifactId> <name>FirstSpiritWeb</name> <!-- if no packaging is named it will default to "jar", where each packaging type contains a list of goals to bind to a particular build phase --> <packaging>war</packaging> <licenses> <license> <name>Bosch Corporate License</name> <url>http://www.bosch.com</url> <distribution>repo</distribution> <comments>A Bosch corporate license</comments> </license> </licenses> <organization> <name>Robert Bosch GmbH</name> <url>http://www.bosch.com</url> </organization> <developers> <developer> <id>kih1fe</id> <name>Holger King</name> <email>Holger.King@de.bosch.com</email> <url>http://www.bosch.com</url> <organization>Robert Bosch GmbH</organization> <organizationUrl>http://www.bosch.com</organizationUrl> </developer> </developers> <version>1.0.0-BUILD-SNAPSHOT</version> <properties> <!-- to prevent encoding warnings during a maven run --> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> <org.springframework-version>3.1.1.RELEASE</org.springframework-version> <org.aspectj-version>1.6.10</org.aspectj-version> <org.slf4j-version>1.6.6</org.slf4j-version> </properties> <dependencies> <!-- FirstSpirit --> <dependency> <!-- scope sets how the dependency is handled in the package --> <groupId>de.espirit.firstspirit</groupId> <artifactId>fs-webrt</artifactId> <version>4.2.476</version> <scope>provided</scope> </dependency> <dependency> <groupId>de.espirit.firstspirit</groupId> <artifactId>fs-access</artifactId> <version>4.2.476</version> <scope>provided</scope> </dependency> <dependency> <groupId>firstspirit.personalisation</groupId> <artifactId>FIRSTpersonalisation</artifactId> <version>2.0.20</version> <scope>compile</scope> </dependency> <!-- Spring --> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-context</artifactId> <version>${org.springframework-version}</version> <exclusions> <!-- Exclude Commons Logging in favor of SLF4j --> <exclusion> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-webmvc</artifactId> <version>${org.springframework-version}</version> </dependency> <!-- AspectJ --> <dependency> <groupId>org.aspectj</groupId> <artifactId>aspectjrt</artifactId> <version>${org.aspectj-version}</version> </dependency> <!-- Logging --> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.7.2</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl-over-slf4j</artifactId> <version>${org.slf4j-version}</version> <scope>runtime</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> <version>${org.slf4j-version}</version> <scope>runtime</scope> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.15</version> <exclusions> <exclusion> <groupId>javax.mail</groupId> <artifactId>mail</artifactId> </exclusion> <exclusion> <groupId>javax.jms</groupId> <artifactId>jms</artifactId> </exclusion> <exclusion> <groupId>com.sun.jdmk</groupId> <artifactId>jmxtools</artifactId> </exclusion> <exclusion> <groupId>com.sun.jmx</groupId> <artifactId>jmxri</artifactId> </exclusion> </exclusions> <scope>runtime</scope> </dependency> <!-- @Inject --> <dependency> <groupId>javax.inject</groupId> <artifactId>javax.inject</artifactId> <version>1</version> </dependency> <!-- Servlet --> <dependency> <groupId>javax.servlet</groupId> <artifactId>servlet-api</artifactId> <version>2.5</version> <scope>provided</scope> </dependency> <dependency> <groupId>javax.servlet.jsp</groupId> <artifactId>jsp-api</artifactId> <version>2.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>javax.servlet</groupId> <artifactId>jstl</artifactId> <version>1.2</version> </dependency> <!-- Test --> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.7</version> <scope>test</scope> </dependency> <!-- JAX-WS --> <dependency> <groupId>com.sun.xml.ws</groupId> <artifactId>jaxws-rt</artifactId> <version>2.2.7</version> <scope>compile</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-simple</artifactId> <version>1.7.2</version> </dependency> </dependencies> <build> <finalName>FirstSpiritWeb</finalName> <defaultGoal>compile</defaultGoal> <sourceDirectory>src/main/java</sourceDirectory> <testSourceDirectory>src/test/java</testSourceDirectory> <outputDirectory>target/main</outputDirectory> <testOutputDirectory>target/test</testOutputDirectory> <pluginManagement> <!-- plugins are artifacts that provide goals for Maven. Where a plugin may have one or more goals. These goals can be bound to Maven build lifecycles phases. --> <plugins> <plugin> <artifactId>maven-eclipse-plugin</artifactId> <version>2.9</version> <configuration> <additionalProjectnatures> <projectnature>org.springframework.ide.eclipse.core.springnature</projectnature> </additionalProjectnatures> <additionalBuildcommands> <buildcommand>org.springframework.ide.eclipse.core.springbuilder</buildcommand> </additionalBuildcommands> <downloadSources>true</downloadSources> <downloadJavadocs>true</downloadJavadocs> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.5.1</version> <configuration> <source>1.6</source> <!-- this verion also controls the used Eclipse Java version when running "Maven" -> "Update project". It changes the "JRE System Library" version within the "Package Explorer" --> <target>1.7</target> <compilerArgument>-Xlint:all</compilerArgument> <showWarnings>true</showWarnings> <showDeprecation>true</showDeprecation> </configuration> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.2.1</version> <configuration> <mainClass>org.test.int1.Main</mainClass> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.2</version> </plugin> <!-- JAX-WS does not support RPC/ENC based WSDL files, details see: http://java.net/projects/metro/lists/users/archive/2007-01/message/79 --> <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> <!-- binds the plug-in goal to the Maven lifecycle phase. A plug-in can offer a default binding to the lifecycle phase. Details can be found in the "plug.xml" descriptor file of the plug-in. For this plug-in its default phase is: "generate-sources" --> <phase>generate-sources</phase> <!-- To identify which plugins is bound to which phase, use the "help" plugin in combination with goal "effective-pom" --> <goals> <!-- goals are tasks within build phases and can be bound to them --> <goal>wsimport</goal> </goals> </execution> </executions> <configuration> <destDir>${project.build.directory}</destDir> <implDestDir>${project.build.sourceDirectory}</implDestDir> <keep>true</keep> <wsdlFiles> <wsdlFile>UserInfoService_DOC_LIT.wsdl</wsdlFile> </wsdlFiles> <packageName>com.bosch.personalisation</packageName> <verbose>true</verbose> </configuration> <!-- if you want to use a specific version of JAX-WS, you can do so like this --> <dependencies> <dependency> <groupId>com.sun.xml.ws</groupId> <artifactId>jaxws-tools</artifactId> <version>2.2.7</version> <exclusions> <exclusion> <groupId>org.jvnet.staxex</groupId> <artifactId>stax-ex</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.jvnet.staxex</groupId> <artifactId>stax-ex</artifactId> <version>1.7.1</version> <exclusions> <exclusion> <groupId>javax.xml.stream</groupId> <artifactId>stax-api</artifactId> </exclusion> </exclusions> </dependency> </dependencies> </plugin> </plugins> </pluginManagement> </build> </project> Von: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx] Im Auftrag von Anders Hammar
You need to edit the pom. It controls this. You initial pom xml snippet looked ok (although it lacks the id element), but I would need to see the complete pom. Actually, what Maven uses is the "effective POM" which should be verified. Btw, as the plugin IS executed when you execute Maven, could you look in the UI to which phase it is bound?
There are two mappings. When talking about phases and the problem you're having we're talking about bindings between a plugin the a phase in the Maven build lifecycle. Then there may also be abinding between the execution of a plugin and the Eclipse build (runtime/incremental) lifecycle. That it not your problem here so I rather not bring that complicated topic into the discussion. /Anders
|