|
| Re: EclipseLink Static Weaving Maven Plugin Lifecycle Mapping Problem [message #1735659 is a reply to message #1734749] |
Tue, 21 June 2016 16:50  |
 Jorge Campins
Messages: 2
Registered: June 2016 |
Junior Member |
|
|
I could finally solve the problem. I had to add a lifecycle-mapping plugin to the <pluginManagement> of the <build> of my project's pom.xml. Now the <build> looks like this:
<build>
<plugins>
<!-- some plugins -->
<plugin>
<groupId>de.empulse.eclipselink</groupId>
<artifactId>staticweave-maven-plugin</artifactId>
<version>1.0.0</version>
<executions>
<execution>
<phase>process-classes</phase>
<goals>
<goal>weave</goal>
</goals>
<configuration>
<logLevel>INFO</logLevel>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.eclipse.persistence</groupId>
<artifactId>org.eclipse.persistence.jpa</artifactId>
<version>2.6.1</version>
</dependency>
</dependencies>
</plugin>
<!-- some more plugins -->
</plugins>
<pluginManagement>
<plugins>
<!--
This plugin's configuration is used to store Eclipse m2e settings only.
It has no influence on the Maven build itself.
-->
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>de.empulse.eclipselink</groupId>
<artifactId>staticweave-maven-plugin</artifactId>
<versionRange>[1.0,)</versionRange>
<goals>
<goal>weave</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute/>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
I found the solution here.
BTW, it certainly wouldn't hurt to add a comment about this in the Configuring Static Weaving page of the wiki.
[Updated on: Tue, 21 June 2016 19:23] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02796 seconds
] 
Search
Help
Register
Login
Home
