updated TracAPI form 3.0.10 to 3.0.11; here to the release notes:

We have released a new version of the TracAPI 3.0.11 that is is 100%
compatible with the previous 3.0.x releases [1].

This is a final version. It fixes bugs in the implementation and it adds
a some features. These features add methods to the API, but they keep
the backward compatibility. This version provides a new JavaDoc version [2].

  1) Features

  - Adding the method IRace.setInitialized(boolean) that allows to load
control point positions although the race is not initialized (Requested
by Jorge Piera, 17/05/2015)

  1) Bugs

   - The subscription library sends (per each control point) an
"ControlPointPosition" event with the positions  of the parameters with
a time stamp equals to the tracking start time. If the control  point
is static (it doesn't have a tracker), it means that this control won't
exist until the tracking start time arrives: it is  not possible to open
a subscription connection before the tracking start time and see the
control point. But  if the control is static,  it has to exist during
all the event. Now when a control is static, the subscription library
sends a "ControlPointPosition" event with the event start time and then
it sends other "ControlPointPosition"  event with the tracking start
time. It allows to connect with future races and see the static controls
(Requested by Jakob Odum, 25/02/2015)

  - It is possible to add two or more subscriptions for the same
subscriber (Reported by Jorge Piera, 02/05/2015)

  - If a race is in a not initialized state and it is loaded using the
parameters file, the library assumes that the consumer application wants
to load the race and it changes its initialized attribute to true. This
assumption is  wrong. Now, if a race is not initialized it will continue
being uninitialized until the event administrator changes its state to
initialized (Reported by Axel Uhl, 17/05/2015)

java/com.tractrac.clientmodule/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: TracTrac Client module
 Bundle-SymbolicName: com.tractrac.clientmodule
-Bundle-Version: 3.0.10
+Bundle-Version: 3.0.11
 Bundle-RequiredExecutionEnvironment: JavaSE-1.8
 Bundle-ClassPath: .,
  lib/TracAPI.jar

java/com.tractrac.clientmodule/README.txt

@@ -16,6 +16,39 @@ It contains also some files:
  - test.sh -> script that compiles the code in the src folder, creates the test.jar library and execute the code of the example.
  - Manifest.txt -> manifest used to create the test.jar file
  
+********************************************
+************* TracAPI 3.0.11 ***************
+********************************************
+This is a final version. It fixes bugs in the implementation and it adds a some features. 
+These features add methods to the API, but they keep the backward compatibility. 
+This version provides a new JavaDoc version.
+
+Release date: 27/05/2015
+Build number: 10715
+
+ 1) Features 
+ 
+ - Adding the method IRace.setInitialized(boolean) that allows to load control point positions despite of
+ the race is not initialized (Requested by Jorge Piera, 17/05/2015)
+ 
+ 1) Bugs 
+ 
+  - The subscription library sends (per each control point) an "ControlPointPosition" event with the positions 
+ of the parameters with a time stamp equals to the tracking start time. If the control  point is static (it 
+ doesn't have a tracker), it means that this control won't exist until the tracking start time arrives: it is 
+ not possible to open a subscription connection before the tracking start time and see the control point. But 
+ if the control is static,  it has to exist during all the event. Now when a control is static, the subscription 
+ library sends a "ControlPointPosition" event with the event start time and then it sends other "ControlPointPosition"
+ event with the tracking start time. It allows to connect with future races and see the static controls (Requested 
+ by Jakob Odum, 25/02/2015)
+   
+ - It is possible to add two or more subscriptions for the same subscriber (Reported by Jorge Piera, 02/05/2015)
+ 
+ - If a race is in a not initialized state and it is loaded using the parameters file, the library assumes that 
+ the consumer application wants to load the race and it changes its initialized attribute to true. This assumption 
+ is  wrong. Now, if a race is not initialized it will continue being uninitialized until the event administrator 
+ changes its state to initialized (Reported by Axel Uhl, 17/05/2015)
+ 
 ********************************************
 ************* TracAPI 3.0.10 ***************
 ******************************************** 

java/com.tractrac.clientmodule/pom.xml

@@ -8,6 +8,6 @@
     <version>1.0.0-SNAPSHOT</version>
   </parent>
   <artifactId>com.tractrac.clientmodule</artifactId>
-  <version>3.0.10</version>
+  <version>3.0.11</version>
   <packaging>eclipse-plugin</packaging>
 </project>