| -- Option A: Import your project into Eclipse (recommended) -- | |
| Configure Eclipse following the instructions at | |
| http://code.google.com/p/google-web-toolkit/wiki/WorkingWithMaven#Using_Maven_with_Google_Plugin_for_Eclipse | |
| In Eclipse, go to the File menu and choose: | |
| File -> Import... -> Existing Maven Projects into Workspace | |
| Select the directory containing this file. | |
| Click Finish. | |
| You can now browse the project in Eclipse. | |
| Now, you need to enable m2Eclipse's annotation processing functionality. | |
| Under project properties, select Maven > Annotation Processing > Enable Project-Specific Settings, | |
| and choose the "Automatically configure JDT APT". Click "Finish", and then right-click on the project, | |
| and select click Maven > Update project. | |
| To launch your web app in GWT development mode (see note below if you | |
| have gae.home set in settings.xml): | |
| Go to the Run menu item and select Run -> Run as -> Web Application. | |
| If prompted for which directory to run from, simply select the directory | |
| that Eclipse defaults to. | |
| You can now use the built-in debugger to debug your web app in development mode. | |
| GWT developers (those who build GWT from source) may add their | |
| gwt-user and gwt-dev projects to this project's class path in order to | |
| use the built-from-source version of GWT instead of the version | |
| specified in the POM. | |
| Select the project in the Project explorer and select File > Properties | |
| Select Java Build Path and click the Projects tab | |
| Click Add..., select gwt-user and gwt-dev, and click OK | |
| Still in the Java Build Path dialog, click the Order and Export tab | |
| Move gwt-dev and gwt-user above Maven Dependencies | |
| GWT developers can also use tools/scripts/maven_script.sh to push their | |
| own GWT jars into their local maven repo. | |
| -- Option B: Build from the command line with Maven -- | |
| If you prefer to work from the command line, you can use Maven to | |
| build your project (http://maven.apache.org/). You will also need Java | |
| 1.6 JDK. Maven uses the supplied 'pom.xml' file which describes | |
| exactly how to build your project. This file has been tested to work | |
| against Maven 2.2.1. The following assumes 'mvn' is on your command | |
| line path. Also, see note below if you have gae.home set in settings.xml. | |
| To run development mode use the Maven GWT Plugin. | |
| mvn gwt:run | |
| To compile your project for deployment, just type 'mvn package'. | |
| For a full listing of other goals, visit: | |
| http://mojo.codehaus.org/gwt-maven-plugin/plugin-info.html | |
| -- Important Note: | |
| The gae-maven-plugin requires a locally extracted copy of the App | |
| Engine SDK in order to run. The gae:unpack goal can do this for you | |
| automatically, by downloading and extracting the contents of | |
| com.google.appengine:appengine-java-sdk:zip into your local maven | |
| repository. The mobilewebapp POM should take care of this, as it | |
| includes the gae:unpack goal. However, if you have gae.home set in | |
| your settings.xml, it won't work properly. The gae:unpack goal will | |
| only work correctly if sdkDir / gae.home are not set. For more info, | |
| see this bug report | |
| (https://github.com/maven-gae-plugin/maven-gae-plugin/issues/8) | |
| against the maven-gae-plugin. |