On Sun, 18 Feb 2018 13:50:26 +0000, sebb wrote:
On 18 February 2018 at 13:46, Thomas Vandahl <t...@apache.org> wrote:
On 18.02.18 14:20, Rob Tompkins wrote:
Not quite because our release process isn’t precisely the same as
what maven does. Hence, our release plugin strives to be a shim for
our site and distribution files. But yes, I agree that “mvn deploy”
should essentially do everything you need.
The Maven release process is not the same as the standard ASF release
process.
In particular it does not handle releases to the ASF mirror system.
Raises another question: Is it good or bad? :-)
Why, being an Apache project, can it derogate from the standard
process?
Gilles
Doesn't everyone complain what a PITA the Commons release process
is?
Why exactly do we try to implement our own release plugin instead of
following the standards? Releasing a component should not require a
Ph.D, IMO
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
