Conflicts:
java/com.sap.sailing.gwt.ui.test/.gitignore
java/com.sap.sailing.gwt.ui.test/META-INF/MANIFEST.MF
java/com.sap.sailing.server.api/.project
java/com.sap.sailing.server.test/META-INF/MANIFEST.MF
java/com.sap.sailing.server/META-INF/MANIFEST.MF
java/com.sap.sailing.server/SailingServer (No Proxy).launch
java/com.sap.sailing.server/SailingServer (No Proxy, No Tests).launch
java/com.sap.sailing.server/SailingServer (No Proxy, Remote Debug SAP VM).launch
java/com.sap.sailing.server/SailingServer (Proxy).launch
java/com.sap.sailing.server/src/com/sap/sailing/server/impl/Activator.java
We suspect the course configuration / RouteData event not to have been
sent when one race changed course in flight. This log may help to
identify what went wrong.
gpsPerRace service which does deliver the GPS coordinates; this latter service hasn't
been aligned with the Xcelsius requirements yet and is merely a code sample for accessing
the tracking information about positions.
Preparing for the possibility of other wind receivers, trying to keep the services and
their APIs independent of the receiving path leading via Expedition, UDP and such.
Introduced the new bundle/system property expedition.udp.port which is now used to
determine the port on which the expedition receivers listen for inbound wind data