I've made a change in the integration shared pom.xml to use the latest non-snapshot javaee artifacts (bottom of message). Some questions: - Heiko, is the ejb3/ws spi going to live in the integration module? - Jesper since you are working on the JCA spi, when done, can you take ownership of http://jira.jboss.com/jira/browse/JBAS-5288 - Upgrade jboss-integration to 5.0.0.CR1 - Do we rev-up all spis when making a new integration project release? (I assume yes) - We probably need a JIRA project to track this. - Who should be the owner of it? Or should we have owners for the individual spis - If AS uses the aggregate org.jboss:jboss-integration, why it needs to import org.jboss:jboss-classloading-spi org.jboss:jboss-corba-ots-spi org.jboss:jboss-transaction-spi and not org.jboss:jboss-deployment-spi org.jboss:jboss-jca-spi In general, I find the maven notion of aggregation weak as it doesn't seem to establish the association between the aggregate and the artifacts it contains (i.e. that org.jboss:jboss-integration:jar contains/replaces the other 5 artifacts at specific versions) --- Modified: projects/integration/trunk/build/pom.xml =================================================================== --- projects/integration/trunk/build/pom.xml 2008-04-22 12:06:25 UTC (rev 72567) +++ projects/integration/trunk/build/pom.xml 2008-04-22 12:27:36 UTC (rev 72568) @@ -90,12 +90,12 @@ <dependency> <groupId>org.jboss.javaee</groupId> <artifactId>jboss-jca-api</artifactId> - <version>1.5.0-SNAPSHOT</version> + <version>1.5.0.CR1</version> </dependency> <dependency> <groupId>org.jboss.javaee</groupId> <artifactId>jboss-transaction-api</artifactId> - <version>1.0.1-SNAPSHOT</version> + <version>1.0.1.CR1</version> </dependency>