[jboss-dev] JB5 Beta3 library dependencies

Tracking down the various dependencies for JB5 Beta3. http://jira.jboss.com/jira/browse/JBAS-4562 https://svn.jboss.org/repos/jbossas/trunk/build/build-thirdparty.xml - We have 10 components at snapshot level. They must reach at least a Beta state until mid-September. Can the respective owners verify they can deliver on time and make sure the updates are tracked with subtasks in JIRA (JBAS-4562), including any transitive dependencies those component may have? <componentref name="jboss/aop" version="snapshot"/> <componentref name="jboss/integration" version="snapshot"/> <componentref name="jboss/jboss-jaspi-api" version="1.0-SNAPSHOT"/> <componentref name="jboss/jboss-javaee" version="5.0.0-SNAPSHOT"/> <componentref name="jboss/jboss-security-spi" version="2.0.1-SNAPSHOT"/> <componentref name="jboss/jbosssx" version="2.0.1-SNAPSHOT"/> <componentref name="jboss/jbosssx-client" version="2.0.1-SNAPSHOT"/> <componentref name="jboss/jbossts" version="snapshot"/> <componentref name="jboss/messaging" version="snapshot"/> <componentref name="jboss/microcontainer" version="snapshot"/> - What other component updates are required? Are those entered in JIRA as well? For the time being we have: Hibernate Annotations 3.3.1 (from 3.2.1) Hibernate Entity Manager 3.3.2 (from 3.2.1) What about jgroups 2.5 ? (now at 2.4.1.SP3). Is something else missing? Any objections on including Hibernate Validator? - Synch with AS 4.2.x xdoclet could go to 1.2.3 (from 1.2b3) remoting to 2.2.1, or 2.2.2 when available (now at 2.2.0.SP4) - Removals. Are the following *really* needed? Most do not exist at all in 4.2.x. wutka-dtdparser backport-concurrent jbossretro apache-myfaces commons-el easymock ehcache sleepycat spring jbpm opensaml - Inconsistencies Don't know how we've managed but we have *two* version of dom4j. Interestingly enough, the last wins: <componentref name="dom4j" version="1.6.1-brew"/> <componentref name="dom4j" version="1.6.1jboss"/> I'm inclined to keep the brew'ed one (used in 4.2.x, too) or does someone remember what's special with the 1.6.1jboss one? Another inconsistency is that JBM brings in the old JBoss Common 1.2.0.GA in thirdparty, although we are using the Common 2.x series. Not sure if it has any other implications. Cheers /Dimitris -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Dimitris Andreadis JBoss AS, Project Lead JBoss, a Division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx