Many AS Components are currently bound to the AS Release Cycle. ie: <dependency> | <groupId>org.jboss.jbossas</groupId> | <artifactId>jboss-as-aspects</artifactId> | <version>${project.version}</version> | </dependency> ...where ${project.version} is currently 5.0.0-SNAPSHOT. This introduces the following: 1) Whereas AS Components are bound to AS Release Cycle 2) ...And whereas AS inherits AS Component dependencies from "dependency-matrix" 3) ...And whereas Consumers of AS Components inherit dependencies from "dependency-matrix" 4) Therefore AS Consumers are bound to a valid release of AS Use Case: 1) We release AS 5.0.0.GA 2) 2 weeks later, AS dependency-matrix is now in 5.0.1-SNAPSHOT 3) We want to release EJB3 RC13, which requires changes introduced to jboss-as-aspects after AS 5.0.0.GA shipped 4) We'd have to release a new version of jboss-as-aspects (5.0.1) and jboss-as-dependency-matrix (5.0.1), but no changes to AS. This would put the current versioning (binding AS Components to SA Version) out of sync. So we need for all components of AS to have independent release cycles. Which also begs the question: if that's possible, shoudn't each component also have its own SVN structure (trunk, branches, tags)? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138141#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...