@Tibor: I agree merging both in one "super" command can be neat (I always run both at once typically) but I disagree with last parts "skip the test" - maven is also there to enforce tests as a good practise, if you don't automatically test it you can configure maven to skip tests for the release but it is at your own risk, can be fine or not - and "skip the deploy" - here again you can configure maven to do it if you need but maven must respect the build attached artifact.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le ven. 4 oct. 2019 à 11:22, Tibor Digana <tibordig...@apache.org> a écrit : > It would be worth to add a new goal called "release" to the > maven-release-plugin which merges "prepare" and "perform". > We developers in companies use both goals prepare and perform immediately > together because for us two goals do not make sense. > Two goals make sense for those who can wait days to start manual tests of > the TAG but we don't! > > We are testing the JAR libraries beforehand and then we evaluate the > quality/manual tests with SNAPSHOT whether it makes sense to start the > release process in CLI. > If there are web archives, the prepare phase would be enough because > deployment in Nexus is useless nothing but the TAG itself and Continuous > Delivery. > > On Fri, Oct 4, 2019 at 8:34 AM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > > > Hi Marco, > > > > I have 2 thoughts reading your post: > > > > 1. Should be enforced by an extension (sonatype plugin if target is > > central?) > > 2. It likely misses a few phases compared to maven release plugin which > > validates the release can be done (including tests) and runs the tests on > > the tag as well > > > > Now if 200 lines of xml can be replaced by a single extension I am +1000 > on > > that track > > > > Le ven. 4 oct. 2019 à 08:24, Marco Schulz <marco.sch...@outlook.com> a > > écrit : > > > > > Hello Maven Dev & Community > > > > > > Sine a long time I thought, it would be cool to have a well defined > > > process to > > > prepare a release of an artifact and deploy it on mvn central. Now I > got > > a > > > bit > > > time to formulate a short proposal of my idea. I published a > description > > > of my > > > thought on my bolg: > > > https://enrebaja.wordpress.com/2019/10/03/next-generation-maven/ > > > > > > A poll is also created, may to see what other people think about it. > > > Please feel > > > free to leave also comments, every feedback is welcome. > > > > > > warm regards & thanks to the maven dev team for the great job they do. > > > .marco (@ElmarDott) > > > > > > -- > > > > > > > > > ________________________________________________________________________________ > > > Dipl. Inf. Marco Schulz (MSc) > > > > > > Expert for (WEB) Enterprise Applications > > > - worldwide - > > > + Project Manager + Consultant + Writer + Speaker + Trainer + > > > > > > > > > > > > [Contact]_______________________________________________________________________ > > > > > > WhatsApp : +52 (1) 221 200 61 37 :: Mexico > > > Cell : +49 (0) 163 69 18 445 :: Germany > > > E-Mail : marco.sch...@outlook.com > > > > > > Blog : https://enRebaja.wordpress.com > > > twitter : https://twitter.com/ElmarDott > > > tumblr : https://elmardott.tumblr.com > > > facebook : https://www.facebook.com/elmar.dott > > > > > > > > > > > > [Services]______________________________________________________________________ > > > > > > + Individual software development > > > + Software Project Management > > > + Build-, Configuration-, & Delivery Management > > > + Release Management > > > + Business Analysis > > > + Software Architecture > > > + Process Automation > > > > > > > > > ________________________________________________________________________________ > > > This message is intended only for the use of the individual or entity > to > > > which > > > it is addressed, and may contain information that is privileged, > > > confidential > > > and that may not be made public by law or agreement. If you are not the > > > intended > > > recipient or entity, you are hereby notified that any further > > > dissemination, > > > distribution or copying of this information is strictly prohibited. > > > If you have received this communication in error, please contact us > > > immediately > > > and delete the message from your system. > > > > > > > > >
