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

"pgier" wrote : For the release of javaee, should each of the sub-projects to use https://svn.jboss.org/repos/jbossas/projects/javaee/tags/ | as the base directory? | | So we end up with something like ? | tags/jboss-javaee-5.0.0.Beta | tags/jboss-servlet-api-2.5.Beta | tags/jboss-ejb-api-3.0.0.Beta | etc.. | I would just have the https://svn.jboss.org/repos/jbossas/projects/javaee/tags/5.0.0.Beta3/ tag contain the entire project structure that makes up the 5.0.0.Beta3 release, and this would include the various projects with their independent pom versions. It should just be a big bang release. It is likely that many subprojects are not going to change as we go from 5.0.0.Beta3 to 5.0.0.GA, but they should still be revd in terms of the qualifier as the aggregate release is revd. Maybe the aggregate qualifier (Beta3 in this case) should just be appended to all of the subprojects for simplicity. "pgier" wrote : | Another question is do we need to release them all at once? Could we just release the modules as needed, and release the combined jar using previously released versions of the modules? This is mostly an issue of ease of release management vs tracking compatibility. If the projects only change their version when there is a code change, its code should still be under the https://svn.jboss.org/repos/jbossas/projects/javaee/tags/x.y.z for the aggregate release. Maven should simply not re-release the same code. If a project depends on another whose version has changed, its dependency/compatiblity range should be updated and re-released. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082286#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...