[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [release-plugin] TODOs

On Tue, 5 Jun 2018 21:39:01 -0600, Gary Gregory wrote:
On Thu, May 31, 2018 at 3:54 PM, Gilles <gilles@xxxxxxxxxxxxxxxxxxxxx>

On Thu, 31 May 2018 10:57:17 -0600, Gary Gregory wrote:


I think we KISS it for the next release: let's not worry about
projects. One bite at a time ;-)

Maybe I'm missing something (Should I have updated the components
which I maintain in some other way than refer to the newest CP?),
but are you aware that that recent versions have broken what used
to work?[1]
How are we supposed to use CP for multi-modules projects?

Note that you do not have to use our newish release plugin... it works

It worked for you, you mean; I evoked local problems, demonstrated
by maven console logs.
The COMMONSSITE-114 issue was one of incompatibility between maven
and new (or upgraded) plugins; but the requirement was not documented.

COMMONSSITE-115 is still a *blocker* for me.  And I kindly remind that
I've delayed (for more than 6 months now) the release of [RNG] on the
premise that it would serve as a testing ground for ensuring that the
release plugin did not make any wrong assumption about multi-module
Currently, none of the CP versions works for "mvn site" on my machine.

but we are still improving it.

But while developing *common* tools, shouldn't it be ensured that they
do not break the build environment of any released component?






To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx