[jboss-dev-forums] [Design of JBoss Build System] - Re: Getting the release process working with javaee

[pgier]

"scott.stark at jboss.org" wrote : "wolfc" wrote : I modeled the versions in the javaee subprojects to be the same as the spec version. So we should never bump these. Maybe we need a build number in there as well, like in RPMs (jboss-javaee-5.0-1)?
  | Yes, that sounds like a good approach. So while the aggregate may be at Beta3, the subprojects are at the spec version with a build number qualifier. A version like 5.0-a does not match the osgi version conventions we outlined though. It would need to be something like 5.0.0.X-buildnumber as the qualifer portion is free-form and should not impact compatibility comparisons.
  | 

Instead of a build number (1, 2, 3, etc..) would it make sense to just append the aggregate release number?  So for example jboss-ejb-api 3.0.0.X-5.0.0.Beta3?
We should be able to do something like this in each of the modules.

  | <version>3.0.0.X-${project.parent.version}</version>
  | 
This way we wouldn't have to worry about continually updating the build number.

Or we could just keep the build number as a property in the aggregate.  So the modules would have:

  | <version>3.0.0.X-${buildNumber}</version>
  | 
And ${buildNumber} would be a property set in the parent pom.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082652#4082652

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082652