On 4/1/07, Torsten Curdt [EMAIL PROTECTED] wrote:
I've noticed that the plugin versions are not specified in the
commons parent pom. From my experience this is a *really* bad idea as
maven then picks the most recent from local repository. Which again
can easily lead to inconsistent site builds
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability. Otherwise we just deal
with whatever pain Maven is throwing everyone's way and yell at them
to fix.
Er why? It is not our job to be gump and test commons builds
On 02.04.2007, at 09:49, Stephen Colebourne wrote:
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability.
...and then have the project define the reports they want?
Otherwise we just deal
with whatever pain Maven
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
On 02.04.2007, at 09:49, Stephen Colebourne wrote:
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability.
...and then have the project define the reports they
Torsten Curdt wrote on Sunday, April 01, 2007 2:17 PM:
I've noticed that the plugin versions are not specified in the
commons parent pom. From my experience this is a *really* bad
idea as
maven then picks the most recent from local repository. Which again
can easily lead to inconsistent site
Henri Yandell wrote:
On 4/2/07, Torsten Curdt [EMAIL PROTECTED] wrote:
On 02.04.2007, at 09:49, Stephen Colebourne wrote:
Henri Yandell wrote:
Personally I think we should only have the plugins defined if the
release jar itself needs them for stability.
...and then have the project define
Torsten Curdt wrote:
I've noticed that the plugin versions are not specified in the commons
parent pom. From my experience this is a *really* bad idea as maven then
picks the most recent from local repository. Which again can easily lead
to inconsistent site builds across the team. So if no
I've noticed that the plugin versions are not specified in the
commons parent pom. From my experience this is a *really* bad idea as
maven then picks the most recent from local repository. Which again
can easily lead to inconsistent site builds across the team. So if no
one objects I will
