I have a nasty feeling from Googling that this is a common requirement that can't be handled by Maven as it currently stands, but perhaps someone else has managed to address the issue.
We have a number of large projects that we're migrating to Maven (the smallest of them has over a hundred pom.xml files) and due to the workflow that's used here - and changing that workflow isn't an option - we end up needing to handle a very large number of versions (effectively each piece of work creates a new version of the code). This would be a lot easier, of course, if we could define the version in a single location rather than having to do so in every pom.xml - which makes code reviews a nightmare as each review would contain changes to all the poms which may or may not require checking by eye. But it seems like there's no way of doing that: substituting variables doesn't seem to work when specifying the parent version - ideally we'd like to use a system variable to define the version. Has anyone in a similar situation found a satisfactory solution to this problem? Anything that involves changing the hundreds of pom files (even if it's automated) doesn't really help, because of the review problem. At the moment we're tending towards generating the poms through a simple XSL transformation before building, but this isn't ideal either - it would be preferable if there were some way of getting the job done entirely within Maven, without having to worry about a pre-build part of the process. Adrian -- View this message in context: http://www.nabble.com/Defining-version-in-single-location--tp14275006s177p14275006.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
