Why Git-Commit-Id-Maven Cannot Be Used With Best Practices of Maven?

Fleeting

why git-commit-id-maven cannot be used with best practices of maven

Maven says to create a BOM at the root of the project to handle the children versions.

The root of the project is the BOM POM. It defines the versions of all the artifacts that will be created in the library. Other projects that wish to use the library should import this POM into the dependencyManagement section of their POM.

— https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies

But, the dependency mechanism does not allow dynamic versioning.

Maven is not designed for dynamic versions and whenever you try to specify a dynamic version you’ll get ‘version’ contains an expression but should be a constant..

Then, using git-commit-id-maven-plugin looses the dependencyManagement and the BOM, which is very unfortunate….

Permalink