On Feb 18, 2008 4:12 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Hi Wendy > > Did you mean for this to go into Maven parent pom? > > The URL in your change suggests to me that is intended for Maven > components pom. If left in Maven parent pom there will be URL clashes > between say Maven 2.1 and Maven Project Info reports Plugin 2.1
I don't expect it to actually be used. Our release instructions say to define a deploy.altRepository property in settings.xml, and (at least for plugins) the release plugin is configured to use that. I want it in the parent pom to prevent any inadvertent publishing directly to m2-ibiblio-rsync-repository (which should never be published to directly, all releases should be staged for review.) And if it does somehow get used, the version number will keep _most_ things separate. If a sub-project does want a shared staging area, it can override this in the top-level pom for that sub-project. Archiva does it this way, see http://people.apache.org/builds/maven/archiva/ (which we need to clean up!) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
