[jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-1341) pom cleanup to get closer to a first tagged release

[ http://jira.jboss.com/jira/browse/EJBTHREE-1341?page=all ] Dimitris Andreadis closed EJBTHREE-1341. ---------------------------------------- Resolution: Done I've pointed ejb3/build/pom.xml to latest jboss-metadata 1.0.0.Beta11 (from Beta9) ejb3/transactions/pom.xml - switched the aspects from snapshot to 1.0.0.Beta1 Changed ejb3/core/pom.xml: - jboss-vfs 2.0.0.Beta8 -> Beta11 - org.jboss.jbossas:main,system,system-jmx,mbeans,j2se to the previous 5.0.0.Beta4 instead of 5.0.0-SNAPSHOT and created a reminder task: http://jira.jboss.com/jira/browse/EJBTHREE-1340 Other inconsistencies I've found: 1) A tagged release depending on a snapshot(!) - I excluded the snapshot [INFO] +- org.jboss.jbossas:jboss-as-mbeans:jar:5.0.0.Beta4:compile ... [INFO] | \- org.jboss:jboss-test:jar:1.0.5-SNAPSHOT:compile 2) The deprecated jboss-container module is brought in implicitly: [INFO] +- org.jboss.aop:jboss-aop:jar:2.0.0.CR7:compile ... [INFO] | +- org.jboss.microcontainer:jboss-container:jar:2.0.0.Beta9:compile (version managed from 2.0.0.Beta6) I've excluded this as it comes through AOP, but it keeps popping up. The jboss-container module is legacy and is replaced by jboss-mdr/jboss-reflect so that should be replaced in the various projects. I've already done so in jbossxb and jboss-metadata. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira