JAVA-272: To deal with the OSGi/Maven version name incompatibilities, added ability to use a different version name for maven and OSGi. So the Maven POM that we upload would have a version like 2.8.0-RC1 or 2.8.0, while the corresponding Bundle-Version in MANIFEST.MF would be 2.8.0.RC1 or 2.8.0.RELEASE. Hopefully this will work for both Maven and OSGi users, as it's the strategy used by, for example the maven-bundle-plugin

Author: jyemin

build.properties

@@ -16,7 +16,11 @@
 
 javac.source=1.5
 
-lib.version=2.8.0.BUILD-SNAPSHOT
+# IMPORTANT: MAKE SURE YOU CHANGE BOTH lib.version AND lib.version.osi.compat, ACCORDING TO THIS PATTERN
+# lib.version=2.8.0-RC1  ==> lib.version.osgi.compat=2.8.0.RC1
+# lib.version=2.8.0  ==> lib.version.osgi.compat=2.8.0.RELEASE
+lib.version=2.8.0
+lib.version.osgi.compat=2.8.0.RELEASE
 
 compatibility.baseline.version=2.7.3
-url.libbase=http://cloud.github.com/downloads/mongodb
+url.libbase=http://cloud.github.com/downloads/mongodb

build.xml

@@ -171,11 +171,11 @@ limitations under the License.
     <target name="jar" depends="compile" description="Create driver jar">
 
         <copy file="src/main/META-INF/MANIFEST.MF" tofile="build/MANIFEST.MF" filtering="true">
-            <filterset><filter token="VERSION" value="${build.conf.lib.version}"/></filterset>
+            <filterset><filter token="VERSION" value="${build.conf.lib.version.osgi.compat}"/></filterset>
         </copy>
 
         <copy file="src/main/META-INF/MANIFEST_BSON.MF" tofile="build/MANIFEST_BSON.MF" filtering="true">
-            <filterset><filter token="VERSION" value="${build.conf.lib.version}"/></filterset>
+            <filterset><filter token="VERSION" value="${build.conf.lib.version.osgi.compat}"/></filterset>
         </copy>
 
         <exec executable="git" output="build/main/git-hash">