THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Once the branch has been created, the release version must be set and committed. The changes should be committed to the release branch.
Ambari 2.8+
Starting with Ambari 2.8, the build process relies on Maven 3.5+ which allows the use of the ${revision} tag. This means that the release version can be defined once in the root pom.xml and then inherited by all submodules. In order to build Ambari with a specific build number, there are two methods:
mvn -Drevision=2.8.0.0.0 ...
- Editing the root
pom.xmlto include the new build number<revision>2.8.0.0-SNAPSHOT</revision>
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
# Update the release version
mvn versions:set -DnewVersion=2.2.0.0.0
pushd ambari-metrics
mvn versions:set -DnewVersion=2.2.0.0.0
popd
pushd contrib/ambari-log4j
mvn versions:set -DnewVersion=2.2.0.0.0
popd
pushd contrib/ambari-scom
mvn versions:set -DnewVersion=2.2.0.0.0
popd
pushd docs
mvn versions:set -DnewVersion=2.2.0.0.0
popd
# Update the ambari.version properties in all pom.xml
$ find . -name "pom.xml" | xargs grep "ambari\.version"
./contrib/ambari-scom/ambari-scom-server/pom.xml: <ambari.version>2.1.0-SNAPSHOT</ambari.version>
./contrib/ambari-scom/ambari-scom-server/pom.xml: <version>${ambari.version}</version>
./contrib/views/hive/pom.xml: <ambari.version>2.1.0.0.0</ambari.version>
./contrib/views/jobs/pom.xml: <version>${ambari.version}</version>
./contrib/views/pig/pom.xml: <ambari.version>2.1.0.0.0</ambari.version>
./contrib/views/pom.xml: <ambari.version>2.1.0.0.0</ambari.version>
./contrib/views/storm/pom.xml: <version>${ambari.version}</version>
./contrib/views/tez/pom.xml: <version>${ambari.version}</version>
./docs/pom.xml: <ambari.version>2.1.0</ambari.version>
./docs/pom.xml: <final.name>${project.artifactId}-${ambari.version}</final.name>
# Update any 2.1.0-SNAPSHOT references in pom.xml
$ grep -r --include "pom.xml" "2.1.0-SNAPSHOT" .
# Remove .versionsBackup files
git clean -f -x -d
# Review and commit the changes to branch-X.Y
git commit |
...