>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?
We can put a property in the release section as well that can be overridden I guess. Having consistent overridable properties ASF wide is important as it more easily lets users build and deploy versions internally without hacking the poms. >This is probably moreso for the <repositories> elements - there's a >chance some projects will be referring to snapshots in both places. The current one is a group that is logically combining the old and new repos, there's no reason not to use the r.a.o group for any project instead of p.a.o since it is the only place that will have all snapshots. > > > >> >> + <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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
