Pete - thanks for letting us know about the issue. Given the holidays we're not going to get to this until after the new years. On Dec 24, 2012, at 3:13 PM, Douglas Campos <dcampos(a)redhat.com&gt; wrote: > no, I'm trying to understand how urgent is this (new guy at red hat ;)) > > -- qmx (mobile) > > On 24/12/2012, at 17:42, Pete Muir <pmuir(a)bleepbleep.org.uk&gt; wrote: > >> Up to you. We can push incremental changes out, so you arent blocking other peoples fixes. >> >> On 24 Dec 2012 17:35, "Douglas Campos" <dcampos(a)redhat.com&gt; wrote: >> can this wait until the end of the holiday break? >> >> -- qmx (mobile) >> >> On 24/12/2012, at 12:33, Pete Muir <pmuir(a)bleepbleep.org.uk&gt; wrote: >> >> > RichFaces/Aerogear teams, >> > >> > Due to a mixup [1] the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo. >> > >> > Please can you update src/main/resources/META-INF/maven/archetype-resources.xml and make sure that the jboss-bom-enterprise-version property is set to the 1.0.2.Final-redhat-1: >> > >> > <requiredProperty key="jboss-bom-enterprise-version"> >> > <defaultValue>1.0.2.Final-redhat-1</defaultValue> >> > </requiredProperty> >> > >> > We'll then need you to do a release, and send a pull to stacks.yaml with the new version of your archetype. >> > >> > Thanks! >> > >> > Pete >> > >> > [1] The EAP team weren't checking the archetypes were working, it only got picked up by JBDS QE. We've asked the EAP team to start testing the archetypes as part of the acceptance tests, and notify the JDF team (me and Rafael) of any issues, so that we can go ahead and fix the problems.