Revision: 10609
Author:   [email protected]
Date:     Thu Sep  1 14:59:35 2011
Log:      Edited wiki page WorkingWithMaven through web user interface.
http://code.google.com/p/google-web-toolkit/source/detail?r=10609

Modified:
 /wiki/WorkingWithMaven.wiki

=======================================
--- /wiki/WorkingWithMaven.wiki Thu Sep  1 14:38:04 2011
+++ /wiki/WorkingWithMaven.wiki Thu Sep  1 14:59:35 2011
@@ -60,5 +60,66 @@
In most cases, after making a POM change in Eclipse, you should be able to right-click on the project, then click Maven > Update project configuration and/or Update project dependencies. However, the steps above are the surest way to pick up all changes.

 = Advanced topics =
+
+== POM changes needed for Eclipse Indigo ==
+Due to changes in the m2e Eclipse plugin for Indigo (3.7), plugin execution no longer happens directly, but rather must be configured through m2e's lifecycle-mapping plugin. In order for a plugin to be invoked within Eclipse, you must define a pluginExecution in the lifecycle-mapping plugin corresponding to the execution tag in the plugin definition itself. To achieve this, add a new section within the build section of the POM. The sample below shows the definitions needed to support maven-gae-plugin, maven-datanucleus-plugin (also for App Engine), and exec-maven-plugin, which is used by the new RequestFactoryInterfaceValidator.
+
+{{{
+    <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>org.datanucleus</groupId>
+                    <artifactId>maven-datanucleus-plugin</artifactId>
+                    <versionRange>[1.1.4,)</versionRange>
+                    <goals>
+                      <goal>enhance</goal>
+                    </goals>
+                  </pluginExecutionFilter>
+                  <action>
+                    <ignore></ignore>
+                  </action>
+                </pluginExecution>
+                <pluginExecution>
+                  <pluginExecutionFilter>
+                    <groupId>net.kindleit</groupId>
+                    <artifactId>maven-gae-plugin</artifactId>
+                    <versionRange>[0.7.3,)</versionRange>
+                    <goals>
+                      <goal>unpack</goal>
+                    </goals>
+                  </pluginExecutionFilter>
+                  <action>
+                    <execute />
+                  </action>
+                </pluginExecution>
+                <pluginExecution>
+                  <pluginExecutionFilter>
+                    <groupId>org.codehaus.mojo</groupId>
+                    <artifactId>exec-maven-plugin</artifactId>
+                    <versionRange>[1.2,)</versionRange>
+                    <goals>
+                      <goal>exec</goal>
+                    </goals>
+                  </pluginExecutionFilter>
+                  <action>
+                    <execute />
+                  </action>
+                </pluginExecution>
+              </pluginExecutions>
+            </lifecycleMappingMetadata>
+          </configuration>
+        </plugin>
+      </plugins>
+    </pluginManagement>
+}}}

 == Using a Maven multi-project with GWT ==

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Reply via email to