Ok it's clear, this is the EAP additional value, and it will not affect the community release which continues as usual... so, when i read in the roadmap "7.1.2.Final -> EAP Only" it is just a wrong description of the milestone

Is this still the case? I see in the JIRA for 7.1.2.Final "Tag used by EAP Only". Is 7.1.2.Final already available somewhere? Do we have to build it ourself as the description suggests that JBoss will only tag it?

I have the same question as Frank and Riccardo have asked becuase now that I can also see "7.1.3.Final Only for EAP" I would like to know if I can treat those releases the same as I treated 7.1.Final, 7.1.1.Final etc.

Let's assume I've build JBossAS from Source (after cloning the GIT repo). Which maven artifacts can/should I use when building my (web) app? Will org.jboss.arquillian:arquillian-bom:1.0.0.Final do the job?

Oracle had then done very good pubicity on it and told that they would have maintenance releases of their GlassFish product's open source edition... a promise that they kept as GlassFish has had many corrective patches and even reached version 3.1.2.

JBoss had also promised (at that time) a similar cycle... But the non-availability of 7.1.2.Final and very probably 7.1.3.Final, be it as downloads as well as the Maven central, shows the opposite.

This for me it not only frustrating, but also is a clear indication that I would keep preferring GlassFish to JBoss just for this clearer and better support strategy for open and enterprise users.

Jason, Jaikiran and colleagues: is this really what you want us to do?

Let's please continue that discussion in that other thread. We have a couple of developers who build and run AS7 on Windows without any issues on a daily basis. So we have to figure out if it's your local setup that running into problem.