Search This Blog

Configure gwt-maven-plugin to start classic DevMode instead of SuperDevMode in GWT 2.7.0

In the pom.xml, pluginManagement -> plugins:
<pluginManagement>
    
    <plugins>
        <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>gwt-maven-plugin</artifactId>
            <goals>
               <goal>run</goal>
            </goals>
            <configuration>
                <extraJvmArgs>-Xmx1024m</extraJvmArgs>
                <superDevMode>false</superDevMode>
                <noServer>true</noServer>
            </configuration>
        </plugin>
    </plugins>
</pluginManagement>
Note:noServer is set true which will not start the embedded jetty web server.
For more details about the configuration options for gwt:run goal, run the following command:
mvn help:describe -Dplugin=org.codehaus.mojo:gwt-maven-plugin -Dgoal=run -Ddetail

Maven: no POM for for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available

Solution:
cd /tmp
mvn archetype:generate -DgroupId=org.eclipse.m2e -DartifactId=lifecycle-mapping -Dversion=1.0.0 -DarchetypeArtifactId=maven-archetype-mojo
cd lifecycle-mapping
mvn clean install
mvn install:install-file -Dfile=target/lifecycle-mapping-1.0.0.jar -DpomFile=pom.xml -DcreateChecksum -DlocalRepositoryPath=/path/to/localMavenRepo