what is the benefit in having one version? if you have so many poms that a release would cause too many changes perhaps you need to relook at the reasoning behind it.
The common theme for having one version i have found is a marketing or management requirement... we just have one aggregating project - per deliverable - that has the "RELEASE" version that defines the version of the other libraries that are the deliverables... using the dependency:resolve plugin or one of the graphing plugins floating around you can get the full picture of exactly what is included. That way marketing know whats going on at the "RELEASE" level and the developers know what code is actually deployed (and changed). On Wed, 12 Dec 2007 04:55:47 Adrian Jackson wrote: > Graham Leggett wrote: > > Irritatingly enough it is required under parent, but the release plugin > > "does the right thing" and updates all of these values for you > > automatically each time you make a release. > > Which brings us back to square one: that doesn't work with our workflow, as > it would result in hundreds of changes to pom.xml files for every piece of > work. Ah well, looks like we'll have to go with generating the pom.xml > files at build time... -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
