Ron,

There was a "dual branding" requirement from early on. The community quickstarts are the source of record, and at certain points in the release cycle, and are merged to the product directory where the Maven property values are commented/uncommented. If you look in the pom files, you'll see something like the following:

<!-- Define the version of the JBoss BOMs we want to import to specify tested stacks. -->
<version.jboss.bom>1.0.4.Final</version.jboss.bom>
<!-- Alternatively, comment out the above line, and un-comment the
line below to use version 1.0.4.Final-redhat-1 which is a release certified
to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6
maven repository. -->
<!-- <version.jboss.bom>1.0.4.Final-redhat-1</version.jboss.bom> -->

I guess I don't really understand the issue.

• If you download the community AS 7 quickstarts, they are configured for the community and you follow the instructions for JBoss AS 7.
• If you download the product EAP 6.x quickstarts, they are configured for the product and you follow the instructions for JBoss Enterprise Application Platform 6.

Am I missing something? Or maybe the instructions aren't clear enough?