...
- Install Eclipse (Mars 4.5, Neon 4.6 GWT super dev mode does not start properly)
- Install Google Web Toolkit, Google App Engine SDK, and Google plug-in for Eclipse using Eclipse new software from http://www.gwtproject.org/download.html. Note: if you were using an older version of this plugin you will need to uninstall it and then re-install it to ensure it has GWT 2.8 beta1 support. Another note: Installing the Google App Engine Maven Integration software made Eclipse error when building the SynapseWebClient. It would not work until I uninstalled it.
- Install the Maven2Eclipse plugin: http://download.eclipse.org/technology/m2e/releases
- Create a GitHub user account
- Contributors should fork the repository and submit GitHub Pull Requests for code inclusion.
Set up Git: https://help.github.com/articles/set-up-git
- Import the project as a maven project
- File → Import → Maven → Existing Maven Projects
- Next, in Root Directory enter the local path to your repository clone
- Next, Finish
- You need to make sure the GWT xml files are on the classpath. All of these resources can be found in src/main/resources and src/test/resources directories.
- Right-click on portal (project name) → Build Path → Configure Build Path...
- Remove the "Exclude" filter from the source tab on the src/main/resources and src/test/resources directories.
- We need to tell the GWT Eclipse-plugin that this is a GWT project. Do this by Right-Clicking on the project in the package explorer and select: Google → Web Toolkit Settings...
- From the resulting dialog make sure the "Use Google Web Tookit" check box is selected.
- Also make sure you are using GWT 2.8 beta1
- We need to tell the Google plugin where our web app directory can be found. Right-click on the project in the package explorer and select Properties.
- From the tree on the left of the dialog navigate to Google → Web Application
- Check the the check box: "This project has a WAR directory"
- With the "Browse" button, select "src/main/webapp"
- UN-CHECK the "Launch and deploy from this directory" This is very important, if you keep this checked then Maven will not be able to generate a clean WAR file. If you see "GWT needs to recompile" when you deploy your WAR then you probably have this box checked.
- Now make sure GWT can compile your code
- Right-Click on the project from the package explorer.
- Select Google→GWT Compile...
- Under the "Entry Point Modules" you should see "Portal PortalDebug - org.sagebionetworks.web", if not, then add it with the add button.
- Remove the "Portal - org.sagebionetworks.web" entry.
- The first time you run this you will be asked to select the output directory where GWT will compile the code. You want this to match the Maven WAR output directory, so use "target/portal-<VERSION>-SNAPSHOT"
- If you get compilation errors from the JavaScript validator (i.e. NullPointerException), navigate to the project's properties → JavaScript → Include Path → Source, and exclude all files from the source. If an OutOfMemoryError was thrown while compiling, you can click the "Advanced" tab towards the bottom of the Google → GWT Compile window and add "-Xms512M -Xmx1524M" to the VM arguments to increase heap space.
- If the GWT Compile successfully compiled the 5 permutations, then you're ready to run the application. If your local hardware resources are insufficient to build, try limiting the permutations by editing your Portal.gwt.xml (set <set-property name="user.agent" value="safari"/>)
- Option 1: start from within Eclipse.
- Right-Click on the project in the package explorer
- Select: Run As → Web Application (GWT Super Dev Mode)
- Set the run configuration VM Arguments to the following: "-XX:MaxPermSize=512m -Xms512m -Xmx2048m -XstartOnFirstThread". Also look at your eclipse.ini file (if launching SDM from Eclipse).
- Double-click on the link provided in the Development Mode window to view the portal in your browser. If you get asked what page to start on choose Portal.html.
- Option 2: build and run from the command line.
- Run 'mvn clean install'
- Run 'mvn gwt:run'
- Option 1: start from within Eclipse.
...