Updating onos-change-version to roll fallback version in CoreManger
Change-Id: I5d69a0b3f52d9f0e499663dff46692feb630a0b4
diff --git a/tools/build/onos-change-version b/tools/build/onos-change-version
index 354c9f2..558888b 100755
--- a/tools/build/onos-change-version
+++ b/tools/build/onos-change-version
@@ -28,6 +28,10 @@
sed -i "" -E "s/ -Dversion=.*\"/ -Dversion=$NEW_VERSION\"/" $ONOS_ROOT/tools/test/bin/onos-archetypes-test
sed -i "" -E "s/ONOS_POM_VERSION=.*\"/ONOS_POM_VERSION=\"$NEW_VERSION\"/" $ONOS_ROOT/tools/build/envDefaults
+# Augment fallback version in CoreManager
+sed -i "" -E "s/Version\.version\(\"[^\"]*\"\)/Version.version(\"$NEW_VERSION\")/" \
+ $ONOS_ROOT/core/net/src/main/java/org/onosproject/core/impl/CoreManager.java
+
# Augment the version in archetypes tree.
mvn -f tools/package/archetypes/pom.xml versions:set -DnewVersion=$NEW_VERSION versions:commit
for atype in api bundle cli; do
@@ -35,6 +39,8 @@
sed -i "" -E "1,/<onos.version>/s/<onos.version>[^<]*</<onos.version>$NEW_VERSION</g" $pom
done
+# FIXME do we really want to roll the version with every release?
+# ... we talked about dropping to a 2 place version that rolls independently
pushd tools/package/maven-plugin
mvn versions:set -DnewVersion=$NEW_VERSION versions:commit
popd