Good point, thanks for spotting it. What's the difference between the components from the 6.0 vs 7.0 BOMs with regards to WF 8.0.CR1/Final ?
The 6.0 BOM's parent is boss-eap-bom-parent which contains all of the recommended version numbers of the products for JBoss EAP 6.2.3. The main difference is that these versions do not include any of the new Java EE 7 features available in Wildfly 8.0.0.FInal, it also references older version of Arquillian and other tools.
The 7.0 BOM's parent contains the recommended version numbers of the products for Wildfly 8.0.0.Final which include all of the new Java EE 7 features and the latest release of Arquillian.
The current problem with using the current modeshape-bom-jbossas with WIldfly 8.0.0.Final is that you have to override all of the version numbers of the dependencies you use with the more recent versions if you want to use any of the Java EE 7 features. The alternative is to include the jboss-javaee-7.0-with-tools bom in your pom.xml as well as the modeshape-bom-jbossas but I don't know how maven determines which version to use then there are to conflicting sources, given this I have avoided this approach.
Neither of the above solutions is ideal and currently I am not using the modeshape bom. Instead I have add the javaee-7.0 bom and then just add the 2 mode shape dependencies to my pom.xml separately.
Let me know if this answers your questions.
Yup, makes sense. I'll make sure the jboss-as BOM is updated to use 7.0 BOM's.