jira-importer commented on issue #323: URL: https://github.com/apache/maven-install-plugin/issues/323#issuecomment-2771868405
**[Jimisola Laursen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER281352)** commented This was quite a downer sadly as dynamic versioning would simplify a lot of things for us in our CI/CD. No, there is quite some logic behind getting the version (source code [here](https://github.com/mojohaus/versions/blob/master/versions-maven-plugin/src/main/java/org/codehaus/mojo/versions/DynamicVersioningSCMPlugin.java)) since it's based on tags (semantic versioned such, i.e. x.y.z) and number of commits (for when the current/last commit is not tagged, then number of commits to that tag is counted). Python has this available for build systems poetry([poetry-dynamic-versioning](https://github.com/mtkennerly/poetry-dynamic-versioning) and hatch ([hatch-vcs](https://github.com/ofek/hatch-vcs)). Having dynamic versioning with Maven, i.e. not manually changing {$project.version } but using scm/vcs tags is our preferred choice (minimizing e.g. the risk of creating a release without updating the project.version). And "trigger model rebuild" is not coming with Maven 4? **fingers crossed** So, the only option is to build an extension then? Looked at https://maven.apache.org/guides/mini/guide-using-extensions.html#core-extension before. Would a build extension suffice or does it have to be core extension? Registration of a build extension seems easier to manage. But, if I were to change the goal to an extension, are you then able to configure when you want this and only this extension to be active? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
