as 7.2.0.Final was released as 6.1.0.Alpha you can find it in enterprise maven repository
Thanks, Tomaz, this is helpful but does not fully answer the question.
Having to use non-standard Maven repositories is rather incovenient. If there is a bug in the release process, I can open a JIRA issue and ask for the missing ZIP to be pushed to Central. If this was omitted by design, then there's no point in writing a ticket...
It was done by design in move to provide EAP binaries to developers.
what do you mean by non-standard maven repository?
it is by all means standard maven repository which you can use in your builds http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Alpha1/maven-repository/
just add it as another <repository> in your pom.xml and that is it.
These days where anyone is allowed to push to Central, anything which is not Central is non-standard. You have to add it to your settings, which slows down builds, or set up a local repository manager. Both of which is just unnecessary and makes people's lives harder....
JBoss AS is probably the only community project I know which has a new "feature" of not providing binary releases.
I'm not discussing the RedHat EAP strategy here. The thing I don't get is this: AFAIK JBoss AS/Wildfly is at least to some extent a true community project in the sense that not every committer is a RedHat employee. So how come the community decided or was pushed by RedHat to decide to stop providing binaries? Why would any Open Source Developer agree to such a policy?
What is keeping The Community or selected community members from simply running a build and publishing the binaries to Maven Central?
If JBoss/RedHat cannot be bothered to produce and publish binary builds of JBoss AS 7.2.0, users have to do it for themselves.
Binary distributions can be found here:
If you don't trust the creators, just check out the GitHub repo and run mvn -Prelease install.