Page Comparison

Table of Contents
minLevel 3

Table of Contents
minLevel 3

UI Development

Set up the Maven Build

...

1. Install latest Eclipse
2. Install the Google Plug-in for Eclipse http://www.gwtproject.org/download.html.  Do not include GWT SDK in the install (GWT SDK will be installed by the maven install).  Do not install the Google App Engine Maven Integration.
3. Install the Maven2Eclipse plugin: http://download.eclipse.org/technology/m2e/releases
4. Create a GitHub user account
   
   1. Contributors should fork the repository and submit GitHub Pull Requests for code inclusion.

5. Set up Git: https://help.github.com/articles/set-up-git

6. Import the project as a maven project
   
   1. File → Import → Maven → Existing Maven Projects
   2. Next, in Root Directory enter the local path to your repository clone
   3. Next, Finish 
7. 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. 
   
   1. Right-click on portal (project name) → Build Path → Configure Build Path...
   2. Remove the "Exclude" filter from the source tab on the src/main/resources and src/test/resources directories.
8. 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...
   
   1. From the resulting dialog make sure the "Use Google Web Toolkit" check box is selected.
   2. Also make sure you are using the GWT SDK from your local maven repository (.m2/repository/com/google/gwt)
9. 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.
   
   1.  From the tree on the left of the dialog navigate to Google → Web Application
   2. Check the the check box: "This project has a WAR directory"
   3. With the "Browse" button, select "src/main/webapp"
   4. 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.
10. Now make sure GWT can compile your code
    
    1. Right-Click on the project from the package explorer.
    2. Select Google→GWT Compile...
    3. Under the "Entry Point Modules" you should see "PortalDebug - org.sagebionetworks.web",  if not, then add it with the add button.
    4. Remove the "Portal - org.sagebionetworks.web" entry.
    5. 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"
    6. 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.
11. SWC uses Sass , in order to automatically transpile to css in Eclipse (this is done automatically by maven) we need to add a custom builder:
    1. Install sass: https://sass-lang.com/install
    2. Open the project properties and navigate to Builders
    3. Create a new (Program) Builder, using the installed sass location as the Location value (e.g. /usr/local/bin/sass)
    4. Set the Working directory to the SWC project (e.g. ${workspace_loc:/portal})

    5. Set the following arguments (might vary according to the version):

       Code Block
       --unix-newlines --sourcemap=none --style compressed --default-encoding=UTF-8 --stop-on-error --no-cache --update src/main/webapp/sass:target/portal-develop-SNAPSHOT

       For the current latest version of sass (1.26.8 at the time of writing):
       
       

       Code Block
       --no-source-map --style=compressed --unicode --stop-on-error --update src/main/webapp/sass:target/portal-develop-SNAPSHOT

    If the GWT

    1. 
       

    2. Under Build Options - Allocate Console, Launch in background, and run this builder during all operations listed.
12. If the GWT Compile successfully compiled, then you're ready to run the application.
    
    1. Option 1: start from within Eclipse.
       1. Right-Click on the project in the package explorer
       2. Select: Run As → GWT Development Mode with Jetty, and select Portal.html
       3. Set the run configuration VM Arguments to the following: "-Xms512m -Xmx2048m -XstartOnFirstThread".
       4. Double-click on the link provided in the Development Mode window to view the portal in your browser. 
    2. Option 2: build and run from the command line.
       1. Run 'mvn clean install'
       2. Run 'mvn gwt:run'

...

• Open Preferences
• Navigate to the Workspace preferences: General → Workspace
• Change the Text File Encoding to UTF-8
• Change the New Text File Line Delimiter to Other and select Unix from the drop-down

Automatically generate css files (like swc.css) from sass files in the project (like swc.sass):

...

--unix-newlines
--sourcemap=none
--style compressed
--default-encoding=UTF-8
--stop-on-error
--no-cache
--update src/main/webapp/sass:target/portal-develop-SNAPSHOT

...

Troubleshooting

• Check your exclusion filters through configure build path in Eclipse to assure nothing is excluded, then refresh and clean the SWC project.
• "Could not deserialize" or similar problems in Super Dev Mode are most often fixed by re-building through the command line (running 'mvn clean install')
• (git) Pull the latest changes from the upstream repository.
• Try to rebuild your Eclipse's Portal project and keep your files in place.
• Perform a Maven update.  

...

Set the repository endpoint parameters in your maven settings.xml file. 

To point to staging set:

To point to production set:

...