For the maven-release-plugin (3.0.0) I've started to extract the API to
make it possible to define your own release strategy.
I'm quite interested in the steps you take and if this fits in the
improved design of the plugin.
If we take a look at the Maven Release process, there are still quite some
manual tasks and some of them could be automated, but that wasn't possible
up until now, hence the need for the improved design.
thanks,
Robert
On Fri, 18 May 2018 22:43:31 +0200, Gary Gregory <garydgreg...@gmail.com>
wrote:
On Fri, May 18, 2018 at 2:36 PM, Rob Tompkins <chtom...@gmail.com> wrote:
> On May 18, 2018, at 3:30 PM, Michael Osipov <micha...@apache.org>
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?
We are also committing the RC files and site to the SVN dist repo.
Gary
-Rob
> Michael
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
