maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <>
Subject Re: [maven-scm-api] Looking to perform svn remote move
Date Sat, 19 May 2018 02:00:23 GMT
Le vendredi 18 mai 2018, 22:36:20 CEST Rob Tompkins a écrit :
> > On May 18, 2018, at 3:30 PM, Michael Osipov <> wrote:
> > 
> > Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > > Hello maven guys,
> > > 
> > > Over on commons we’ve been writing our own release-plugin
> > 
> > What is wrong with the current Maven Release Plugin and why are you
> > writing your own whereas we could improve the current one, can't we?
> We are trying to fit the Apache release paradigm where we are dealing with
> assemblies that we don’t want to deliver to Nexus. Further we are
> publishing the site up to our dev dist area for comparison with RC
> validation. We could contribute it back to the release plugin, but I’m not
> sure if it’s sufficiently general. Thoughts?

IIUC, the "release plugin" from Commons provides 3 mojos to prepare 3 
assemblies: it does not replace "release plugin" from Maven, which modifies 
pom.xml to switch from -SNAPSHOT to release version then to next SNAPSHOT

How is Commons release plugin used during a Commons release vs Maven release 
plugin? Do Commons use "mvn release:prepare" then "mvn release:perform", and 
the build in the release profile runs the 3 mojos to get the 3 assemblies?

Because what I see in this Commons release plugin look like custom steps to 
add to Maven release plugin, in addition to currently provided ones: as Robert 
wrote, there is a WIP in Maven release plugin to document how to add new 
steps. The Maven release plugin is already organized in steps, to be flexible, 
but just has not documented how to add new steps.



> -Rob
> > Michael
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message