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



Maven Eclipse set compiler JDK compliance level








The maven project/module created in Eclipse set JAVA 1.5 as the default. You cannot change it via Eclipse project settings (as it will be reverted back to 1.5) when you run Maven -> Update Project. To solve this, you can add the following to the pom.xml:
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>3.3</version>
            <configuration>
                <source>1.6</source>
                <target>1.6</target>
            </configuration>
        </plugin>
    </plugins>
</build>
Or, if you have hierarchical project with modules, you can put it into pluginManagement of the parent project's pom.xml:
<build>
    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.3</version>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>
        </plugins>
    </pluginManagement>
</build>
All the descendant modules will inherit the compiler settings from the parent.

NOTE:

In Eclipse, if the project packaging is pom the compiler settings will not get updated using the above. You will need to change packaging to jar then Update the Maven projects. You can revert back to pom after the compiler settings has been changed.