-
Notifications
You must be signed in to change notification settings - Fork 112
Contributor Setup
##Contributing Source To Project Fork and clone the project using an IDE or terminal.
##Eclipse IDE Setup There are two ways to setup the project, one us using egit-m2e import or Maven import. Or two you can use mvn eclipse:eclipse which manually sets up the project and allows for buildpath overriding.
##1. Eclipse Auto Maven Import Needed: Egit, Egit m2e, GWT plugin
- Fork this project
- Import git clone url project via egit.
- Right click on working space and import maven projects.
- Double check GWT plugin and if GWT is enabled on two projects.
##2. Eclipse Manual Maven Import Setup The manual maven setup will allow you to override the maven dependencies in the build path.
- The goal of these steps below is to setup Eclipse with the built in GWT & GAE library, using the native debugging.
- For the Apis_Maps_Test project
- close eclipse
- goto the console's project path
- mvn eclipse:clean
- mvn eclipse:eclipse
- on build success load eclipse back up
- goto project build path
- in buildpath libraries, remove GWT lib(s) from M2_REPO/com/google/gwtÉ2.5 whatever and remove gwt_dev
- "add library" button on the right, click on it and add the GWT lib
- goto order and export, and push the GWT library just below source folders and on top of maven
- Be sure the JRE is at the bottom of the library order
- Goto the Google.Google Web Application menu on the left, check both boxes. Uncheck the second if you want to build in target
- Goto Web Toolkit men and enable GWT, and select the latest SDK
- Close the build path, then open and double check settings.
- Link up the
###Eclipse Manual Maven Setup Problems When things go awry with the eclipse setup.
- mvn eclipse:clean
- delete .settings folders
- repeat the setup
If there is a problem its most likely a conflict with the GWT libs. Double check the GWT Lib container and the maven depdencies for duplicates.
##Notes
- Please don't code bomb our team. Please pull small sets of changed code.
- Just because you modified something doesn't mean it will make it into the project.
##Sonatype Releasing The maven release plugin will automatically increment the snapshot. Remove batch-mode to manually select the release version.
- export JAVA_HOME=
/usr/libexec/java_home -v 1.6
- mvn clean deploy -Prelease -DskipTests
- mvn release:clean release:prepare --batch-mode -Dgpg.passphrase=xxxxx
- mvn release:perform -Dgpg.passphrase=xxxxxx
- https://oss.sonatype.org/index.html
- close staged release - (login first, then goto staging repositories)
- close release - wait a while and come back and release the closed