Details
-
Task
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.8.0
-
None
Description
It looks like Ambari’s trunk pom.xml has not been updated with a proper version in at least 4 years. It currently still lists trunk as 2.0.0.0-SNAPSHOT:
<groupId>org.apache.ambari</groupId> <artifactId>ambari</artifactId> <packaging>pom</packaging> <name>Ambari Main</name> <version>2.0.0.0-SNAPSHOT</version> <description>Ambari</description>
This poses several problems as we try to make our artifacts more 3rd-party friendly since it becomes ambiguous what other maven projects are actually depending on. We need to change our process to keep this version updated with every release of Ambari. Other Apache projects seem to do this (I took a look at Nifi, Hive, Storm, etc) and in each case, their trunk pom.xml was at least a minor version ahead of their most recent release branch.
- We should change the version specified for Ambari and its submodules to use the next major version after a release, such as 3.0.0.0-SNAPSHOT. Once 3.0 has been released, this will be changed to 4.0.0.0-SNAPSHOT even if there are more builds in the 3.x line off of trunk.
- Maven 3.5.0 allows the ability to specify a <version>${revision}</version> placeholder value in the parent pom.xml which submodules can inherit. This seems cleaner than having all of the submodules updated and checked in using the mvn versions:set -DnewVersion=3.0.0.0-SNAPSHOT command.
- If any submodule inherits from ambari or ambari-project, then they should broadcast their version as the same. This includes submodules such as ambari-utility which are hard coded at 1.0.0.0-SNAPSHOT which makes understanding what actually exists in local repos very difficult.
Attachments
Issue Links
- links to
