How are people updating their pom.xml files with version numbers from
say cruisecontrol?
We have two types of codelines (in perforce) here, project and release
lines. Everything starts out life as a project then over time one (or
more) projects can be integrated to a release line.
I'm curious, we're forcefully editing (with the ant replace task) some
templated version.html files to reflect what version was built. Do I
need to be doing this to the pom.xml files also?
When something is getting built from a project branch, the build number
looks like this:
X.<projectbranchname>.<buildnumber>
So:
8.P000001.1
In the maven world, all the project branches would look like this:
<version>X.X-SNAPSHOT</version
So in the above case -
<version>8.0-P000001-SNAPSHOT</version>
And when that goes to release
<version>8.0.X</version>
Where X is a build number.
This has a problem though - I'll have to remember the dependency order
to build and make sure that module "C" gets built before "B" which is
built before "A" (or the replace at least happens in that order).
So what are people doing for this? Manually updating before every
build? I _really_ don't want to have to go back to that....
