Changes in 29c850b: added debug instructions for gwt

				wiki/howto/development/local-gwt.md
			
          @@ -23,7 +23,9 @@ Add restrictions with the following two tags to reduce the number of permutation

           Those tags must be put into the *.gwt.xml files e.g. "AdminConsole.gwt.xml".

           ## Debugging GWT

          -

          +### Super dev Mode

          +To debug GWT using the super dev Mode start the SailingServer according to your environment, then launch the GWT Sailing SDM in debug mode. After the initial compile all entry points will show up in the development Mode section. Do not use these entry points. Instead, to start debugging the web application open the debug drop down and select ``Debug Configurations..``. In the newly opened menu open the node ``Launch Chrome`` and select the configuration fitting your needs. To start the debug session just press debug.

          +### dev Mode (deprecated)

           One of the great strengths of GWT is the use of Eclipse as a Java source-level debugging environment. To enjoy this feature, launch the SailingServer launch config appropriate for your environment (Proxy / No Proxy), then launch the SailingGWT launch configuration in debug mode. After a while it will show a "Development Mode" view that shows all entry points that have been initialized. Double-click on the one you want to debug, and your default browser (hopefully FireFox, because with other browsers the GWT debug plugin tends to be not very stable or not even present) will open.

           You can set breakpoints in your GWT Java code and inspect values for suspended threads as usual for any Java development.

				wiki/howto/onboarding.md
			
          @@ -150,8 +150,9 @@ Out of the box, multiple settings in Eclipse need to be changed. Go to Window 

              - In the list on the left, click on "Connectors"

              - For TracTrac Events: In the "TracTrac Connections" Form, fill in the JSON URL [http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php](http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php)(all other required information will be filled in automatically)

              - Press "List Races"

          -

          +6. Further useful launch configurations

              - Use SAP JVM Profiler. If you used the script above and installed the SAPJVM instead of the jdk, you can now open the profiling perspective by clicking on Window ⇒ Perspective ⇒ Open Perspective ⇒ Profiling)

          +   - Debugging gwt: For further instructions please see [here](./development/local-gwt.md#Working-with-GET-Locally_Debugging-GWT_Super-dev-Mode)

           ### Build for deployment

           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.

...	...	@@ -23,7 +23,9 @@ Add restrictions with the following two tags to reduce the number of permutation
23	23	Those tags must be put into the *.gwt.xml files e.g. "AdminConsole.gwt.xml".
24	24
25	25	## Debugging GWT
26		-
	26	+### Super dev Mode
	27	+To debug GWT using the super dev Mode start the SailingServer according to your environment, then launch the GWT Sailing SDM in debug mode. After the initial compile all entry points will show up in the development Mode section. Do not use these entry points. Instead, to start debugging the web application open the debug drop down and select ``Debug Configurations..``. In the newly opened menu open the node ``Launch Chrome`` and select the configuration fitting your needs. To start the debug session just press debug.
	28	+### dev Mode (deprecated)
27	29	One of the great strengths of GWT is the use of Eclipse as a Java source-level debugging environment. To enjoy this feature, launch the SailingServer launch config appropriate for your environment (Proxy / No Proxy), then launch the SailingGWT launch configuration in debug mode. After a while it will show a "Development Mode" view that shows all entry points that have been initialized. Double-click on the one you want to debug, and your default browser (hopefully FireFox, because with other browsers the GWT debug plugin tends to be not very stable or not even present) will open.
28	30
29	31	You can set breakpoints in your GWT Java code and inspect values for suspended threads as usual for any Java development.

...	...	@@ -150,8 +150,9 @@ Out of the box, multiple settings in Eclipse need to be changed. Go to Window
150	150	- In the list on the left, click on "Connectors"
151	151	- For TracTrac Events: In the "TracTrac Connections" Form, fill in the JSON URL [http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php](http://germanmaster.traclive.dk/events/event_20120905_erEuropean/jsonservice.php)(all other required information will be filled in automatically)
152	152	- Press "List Races"
153		-
	153	+6. Further useful launch configurations
154	154	- Use SAP JVM Profiler. If you used the script above and installed the SAPJVM instead of the jdk, you can now open the profiling perspective by clicking on Window ⇒ Perspective ⇒ Open Perspective ⇒ Profiling)
	155	+ - Debugging gwt: For further instructions please see [here](./development/local-gwt.md#Working-with-GET-Locally_Debugging-GWT_Super-dev-Mode)
155	156
156	157	### Build for deployment
157	158	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.