On Tue, 5 Jun 2018 21:39:01 -0600, Gary Gregory wrote:
On Thu, May 31, 2018 at 3:54 PM, Gilles
<[email protected]>
wrote:
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
multi-module
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
obviously,
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
projects.
Currently, none of the CP versions works for "mvn site" on my machine.
but we are still improving it.
Great.
But while developing *common* tools, shouldn't it be ensured that they
do not break the build environment of any released component?
Regards,
Gilles
Gary
Thanks,
Gilles
[1] https://issues.apache.org/jira/projects/COMMONSSITE/issues/
COMMONSSITE-114
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
