we talk about the maven-release-plugin, but I think that we should also talk about the release profile = the way we extend the goals run during a non- release build with a few additional goals on a release build
see for example the "apache-release" profile documentation of ASF parent https://maven.apache.org/pom/asf/ By adding a new lifecycle, you would loose the sharing of most steps between non-release and release builds Like Karl Heinz, I really don't get the pain points you're trying to solve Regards Hervé Le jeudi 3 octobre 2019, 17:04:02 CEST Karl Heinz Marbaise a écrit : > Hi, > > first thanks... > > I have several question regarding your blog post ... > > Apart from beeing not accurate in some part I miss one very important thing: > > What is the real problem when doing a release via release plugin etc. > which works well (I haven't said that it could be improved)... > > I want to know what the pain points are ? > > > Kind regards > Karl Heinz Marbaise > > On 03.10.19 15:38, Marco Schulz wrote: > > 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) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
