On 15/06/2007, at 11:23 PM, Jason van Zyl wrote:
On 15 Jun 07, at 4:30 AM 15 Jun 07, Kenney Westerhof wrote:
Yup, I did the same change locally to test something.
Normally we don't want to depend on plexus snapshots since it
imposes a restriction
on the ability to release.
I think we should add the repo in the pom where we need a plexus
snapshot, and remove it
as soon as the dependency is released. Putting it in a parent or
root pom will
promote use of snapshots.
We should have a set standard settings.xml chunk that we use so
that the repositories are not entered into the POM so that when you
go to make releases you don't have to diddle the POM. In addition
we should have a standard snapshot repository as it is so common to
pull in snapshots and just results in lots of busy work add/
removing/adding/removing.
This is totally unnecessary. Consistently defining snapshot plugin
repositories works just fine if you define it to only be used for
snapshots (like we do in the maven parent). If you have no snapshots,
it won't be used.
The two reasons this perception comes about:
- adding plugin repositories in this way is dangerous due to the
unpredictability of versions. We're addressing that differently.
- there was a bug where getting metadata didn't work unless you have
releases set to true. I think that also impacted plugin repositories.
I'm all for using settings to define plugin repositories when you
control the environment. But when random people are grabbing our
project and building it I want mvn install to work out of the box.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
