2/29/2024 0 Comments Maven revision![]() ![]() With the Maven 3.2.1 release and the newly introduced support for Continuous Delivery friendly versions This resulted in the need to run Maven twice: once for updating the version and the again with the To dynamically update the generic version contained in the POM to the new version assigned dynamically for theĬurrent build. Quite the win indeed!īoth original article series and the Final Nail update required the use of the Versions Maven Plugin The reduction in the number of Clean/Compile/Test cycles alone results in a 3x build time improvement!Īnd this doesn't even take into consideration the other adavantages like increased reliability and recoverability. So how big exactly was the improvement of Releases On SteroidsĪnd Final Nail over the Release Plugin? See for yourself: ThisĬoncept permeates through all aspects of the Maven ecosystem, culminating with the monstrosity commonly referred ![]() Maven has traditionally required the version number to be present in the project descriptor (pom.xml). While not perfect, even this minimal implementation warranted this long overdue update to my previous articles. With its 3.2.1 release, Maven finally introduced support for Continuous Delivery friendly versions. Itself and the improvements it provided into the workflow. Maven Release Plugin: The Final Nail in the Coffin that integrated both Git The original series was written for Subversion.īy 2013 Git had taken over the market and so I published an update called It did so in a way that is compatible with Continuous Delivery. Series was to provide a simple and efficient way to produce releases on a Maven project. This is the second major update to a very popular article series titled 'Maven Releases on Steroids' which I originally
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |