jboss-as-dist-7.2.0.Final Maven artifact?

[hwellmann.de]

Maven Central stores all sorts of JBoss AS 7.2.0 artifacts, but the distribution ZIP artifact is missing.

See http://search.maven.org/#search|gav|1|g%3A%22org.jboss.as%22%20AND%20a%3A%22jboss-as-dist%22

Is this a glitch in the release process, or a deliberate omission due to Redhat's new policy of not providing binary public releases?

Best regards,

Harald

[ctomc]

Hi,

as 7.2.0.Final was released as 6.1.0.Alpha you can find it in enterprise maven repository

http://maven.repository.redhat.com/techpreview/eap6/6.1.0.Alpha1/maven-repository/org/jboss/as/jboss-as-dist/7.2.0.Alpha1-redhat-4/

--

tomaz

[hwellmann.de]

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...

Best regards,

Harald

[ctomc]

It was done by design in move to provide EAP binaries to developers.

read more about it at https://community.jboss.org/blogs/mark.little/2013/03/07/eap-binaries-available-for-all-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.

--

tomaz

[hwellmann.de]

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?

[hwellmann.de]

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:

• https://olex-secure.openlogic.com/content/openlogic/jboss/7.2.0.Final/openlogic-jboss-7.2.0.Final-all-bin-1.zip
• http://www.redpill-linpro.com/sites/default/files/node_files/jboss-as-7.2.0.final_.zip

If you don't trust the creators, just check out the GitHub repo and run mvn -Prelease install.

[mlybarger]

i know this post is 5 years old. but i'm looking for jboss as 7.2.Final. both of the links are dead and the git repo doesn't build due to missing mvn dependencies. 

redhat or jboss has "cleaned up" the maven repositories and now this doesn't build....

[ctomc]

There ware some issues with the build at the time already.

But ware related to few tests only.

Usually building with -DskipTests helped.

what is the error you got?

[mlybarger]

Thanks Tomaz, by golly, that worked!