On 14/02/2009, at 10:11 PM, Brian E. Fox wrote:
Isn't modifying the ASF POM premature? I'm not sure if other projects
are using the POM or not (they should be), but they may not be using
this system.
There are a few other projects looking to use the new structure and
this
would make it easier for them to do. Projects not using the new repo
can
continue to use the 4.x versions of the pom. There's no requirement
for
them to have the last parent for these purposes. It's either that or
we
fork the parent. I don't think it's a great idea to require every
project to overload the same things over and over.
I do like the hook to get people to actually use the parent POM, but
at the same time it feels back to front (We probably don't need
another pom release, but if we did that would then have to be a
fork...). What about having them use the properties as their distMgmt
settings for now?
This is probably moreso for the <repositories> elements - there's a
chance some projects will be referring to snapshots in both places.
+ <pluginRepositories>
+ <pluginRepository>
+ <id>apache.snapshots</id>
+ <name>Apache Snapshot Repository</name>
+ <url>http://repository.apache.org/content/groups/snapshots/</
url>
+ <releases>
+ <enabled>false</enabled>
+ </releases>
+ </pluginRepository>
+ </pluginRepositories>
Isn't this badness for pre-Maven 2.0.9 users?
It only applies to building our stuff, which often requires plugin
snapshots anyway. It shouldn't hurt their builds, unless I'm not
thinking of something.
If they haven't given a version for a plugin that is hosted at Apache,
they start getting snapshots resolved for it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
