Fixed list formatting

This commit is contained in:
Axel Uhl committed 2014-04-09 11:46:00 +00:00
1 parent 4d56841c26
commit 9f120545f6
1 file changed
+36 -43
+36 -43
View File
@@ -26,50 +26,43 @@ This document describes the onboarding process for a new team member (developer)
#### Accounts
1. Git Account
- Register yourself as a Git user in the SAP-Git under: https://git.wdf.sap.corp:8080/
- Ask the Git administrator (Axel Uhl) to get on the list of enabled committers
* Register yourself as a Git user in the SAP-Git under: https://git.wdf.sap.corp:8080/
* Ask the Git administrator (Axel Uhl) to get on the list of enabled committers
2. Bugzilla
- Ask the Bugzilla administrator (Frank Mittag, Axel Uhl) to create a bugzilla account for you.
- Bugzilla url: http://sapsailing.com/bugzilla/
* Ask the Bugzilla administrator (Frank Mittag, Axel Uhl) to create a bugzilla account for you.
* Bugzilla url: http://sapsailing.com/bugzilla/
3. Race Analysis user
- Add yourself as an user to the Race Analysis suite by adding a Jetty user in the file
java\target\configuration\jetty\etc\realm.properties
* Add yourself as an user to the Race Analysis suite by adding a Jetty user in the file java\target\configuration\jetty\etc\realm.properties
#### Steps to build and run the Race Analysis Suite
1. Get the content of the git repository
- Generate SSH Keys with "ssh-keygen -t rsa -C "" " command in Cygwin Terminal (Not with Putty!!!)
- Clone the repository to your local file system from `ssh://[SAP-User]@git.wdf.sap.corp:29418/SAPSail/sapsailingcapture.git` or `ssh://[user]@sapsailing.com/home/trac/git`
* Generate SSH Keys with "ssh-keygen -t rsa -C "" " command in Cygwin Terminal (Not with Putty!!!)
* Clone the repository to your local file system from `ssh://[SAP-User]@git.wdf.sap.corp:29418/SAPSail/sapsailingcapture.git` or `ssh://[user]@sapsailing.com/home/trac/git`
2. Check out the 'master' branch from the git repository. The 'master' branch is the main development branch. Please check that you start your work on this branch.
3. Setup and configure Eclipse
- Make absolutely sure to import CodeFormatter.xml (from $GIT_HOME/java) into your Eclipse preferences (Preferences->Java->Code Style->Fortmatter)
- Install the Eclipse GWT-Plugin (now called Google Plugin for Eclipse, you need the Google WebToolkit SDK from the same update site, too)
- Install the Google Android SDK from the same Google Plugin for Eclipse update site
- Install Eclipse eGit (optional)
- Check that JDK 1.7 is available and has been set for compilation in Eclipse
- Check that the both JDKs are available (Windows->Preferences->Java->Installed JREs)
- Check that JDK 1.6 has been matched to JavaSE-1.6 and that JDK 1.7 has been matched to JavaSE-1.7 (...>Installed JREs>Execution Environments)
- It is also possible to match the SAPJVM 6 or 7 to the JavaSE-1.6 (for profiling purposes)
- Go to Windows->Preferences->Google->Errors/Warnings and set "Missing SDK" to "Ignore"
- Import all Race Analysis projects from the `java/` subdirectory of the git main folder
- Import all projects from the `mobile/` subdirectory of the git main folder; this in particular contains the race committee app projects
- Set the Eclipse target platform to race-analysis-p2-ide-local.target (located in com.sap.sailing.targetplatform/definitions)
- Wait until the target platform has been resolved completely
- In the project com.sap.sailing.gwt.ui create a new subfolder "classes" in the folder WEB-INF
- Rebuild all projects
* Make absolutely sure to import CodeFormatter.xml (from $GIT_HOME/java) into your Eclipse preferences (Preferences->Java->Code Style->Fortmatter)
* Install the Eclipse GWT-Plugin (now called Google Plugin for Eclipse, you need the Google WebToolkit SDK from the same update site, too)
* Install the Google Android SDK from the same Google Plugin for Eclipse update site
* Install Eclipse eGit (optional)
* Check that JDK 1.7 is available and has been set for compilation in Eclipse
* Check that the both JDKs are available (Windows->Preferences->Java->Installed JREs)
* Check that JDK 1.6 has been matched to JavaSE-1.6 and that JDK 1.7 has been matched to JavaSE-1.7 (...>Installed JREs>Execution Environments)
* It is also possible to match the SAPJVM 6 or 7 to the JavaSE-1.6 (for profiling purposes)
* Go to Windows->Preferences->Google->Errors/Warnings and set "Missing SDK" to "Ignore"
* Import all Race Analysis projects from the `java/` subdirectory of the git main folder
* Import all projects from the `mobile/` subdirectory of the git main folder; this in particular contains the race committee app projects
* Set the Eclipse target platform to race-analysis-p2-ide-local.target (located in com.sap.sailing.targetplatform/definitions)
* Wait until the target platform has been resolved completely
* In the project com.sap.sailing.gwt.ui create a new subfolder "classes" in the folder WEB-INF
* Rebuild all projects
4. Run the Race Analysis Suite
- Start the MongoDB
- Start the appropriate Eclipse launch configuration (e.g. 'Sailing Server (Proxy)') You´ll find this in the run dropdown
- Run "SailingGWT" in the run dropdown
* Start the MongoDB
* Start the appropriate Eclipse launch configuration (e.g. 'Sailing Server (Proxy)') You´ll find this in the run dropdown
* Run "SailingGWT" in the run dropdown
5. Within the Race Analysis Suite
- For TracTrac Events: (Date 27.11.2012) Use Live URI tcp://10.18.22.156:4412, Stored URI tcp://10.18.22.156:4413, JSON URL http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php
- Press List Races
* For TracTrac Events: (Date 27.11.2012) Use Live URI tcp://10.18.22.156:4412, Stored URI tcp://10.18.22.156:4413, JSON URL http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php
* Press List Races
#### Maven Setup
Copy the settings.xml from the top-level git folder to your ~/.m2 directory and adjust the proxy settings accordingly. Make sure the mvn executable you installed above is in your path. Open a shell (preferrably a git bash or a cygwin bash), cd to the git workspace's root folder and issue "./configuration/buildAndUpdateProduct.sh build". This should build the software and run all the tests. If you want to avoid the tests being executed, use the -t option. If you only want to build one GWT permutation (Chrome/English), use the -b option. When inside the SAP VPN, add the -p option for proxy use. Run the build script without arguments to get usage hints.
@@ -88,20 +81,20 @@ To ensure that all components of the Analysis Suite are working, you should also
- After restarting Eclipse the "Welcome to Android Development" window should help you with installing the Android SDK
- It is also possible to download the Android SDK separately from http://developer.android.com/sdk/index.html ("Use an existing IDE")
2. Setup the Android SDK
- In Eclipse press Window -> Android SDK Manager
- Ensure that everything of "Tools" is installed
- Install everything of "Android 3.2 API 13"
- Optional: it's a good idea to install the newest API Version
- Install "Android Support Library" (Extras), "Google Play Services" (Extras) and "Google USB Driver" (Extras)
* In Eclipse press Window -> Android SDK Manager
* Ensure that everything of "Tools" is installed
* Install everything of "Android 3.2 API 13"
* Optional: it's a good idea to install the newest API Version
* Install "Android Support Library" (Extras), "Google Play Services" (Extras) and "Google USB Driver" (Extras)
3. Import the Android projects into your workspace
- Android projects can be found in the /mobile subdirectory
* Android projects can be found in the /mobile subdirectory
To deploy an Android project (for example com.sap.sailing.racecommittee.app) to a real device:
1. Plug-in the device
- Development mode must be enabled on the device
- For certain device/OS combinations additional device drivers are needed
- You can check if the device is detected correctly by checking the "Devices" tab of the "DDMS" Eclipse perspective.
* Development mode must be enabled on the device
* For certain device/OS combinations additional device drivers are needed
* You can check if the device is detected correctly by checking the "Devices" tab of the "DDMS" Eclipse perspective.
2. Start a run configuration of the project
3. Select your attached device in the device selection screen
4. The app should be started after deployment