EAP 6.2.0 ER4 Maven repo zip does not contain jboss-as-client-all jar which is present in EAP zip (with different name: jboss-client.jar).
This artifact was present in maven repo zip in prior releases ER4 was planned to be build with minimum changes and mainly blocker issues fixes, this is unexpected regression. Example from EAP 6.2.0 ER3 620ER3/jboss-eap-6.2.0.Beta1-maven-repository/org/jboss/as/jboss-as-client-all/7.3.0.Final-redhat-6/jboss-as-client-all-7.3.0.Final-redhat-6.pom 620ER3/jboss-eap-6.2.0.Beta1-maven-repository/org/jboss/as/jboss-as-client-all/7.3.0.Final-redhat-6/jboss-as-client-all-7.3.0.Final-redhat-6.pom.sha1 620ER3/jboss-eap-6.2.0.Beta1-maven-repository/org/jboss/as/jboss-as-client-all/7.3.0.Final-redhat-6/jboss-as-client-all-7.3.0.Final-redhat-6.pom.md5 620ER3/jboss-eap-6.2.0.Beta1-maven-repository/org/jboss/as/jboss-as-client-all/7.3.0.Final-redhat-6/jboss-as-client-all-7.3.0.Final-redhat-6.jar.sha1 620ER3/jboss-eap-6.2.0.Beta1-maven-repository/org/jboss/as/jboss-as-client-all/7.3.0.Final-redhat-6/jboss-as-client-all-7.3.0.Final-redhat-6.jar 620ER3/jboss-eap-6.2.0.Beta1-maven-repository/org/jboss/as/jboss-as-client-all/7.3.0.Final-redhat-6/jboss-as-client-all-7.3.0.Final-redhat-6.jar.md5
Removing this jar was intentional because shaded jars such as this one should not be used from a Maven repository. The purpose of the client-all jar is for use in a non-Maven build. We did some automation improvements to the Maven repo zip and apparently this was fixed due to the automation changes. Was this jar included in EAP 6.1.1?
Yes, this jar was included in 6.1.1 GA: ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10-sources.jar.sha1 ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10.pom.sha1 ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10-sources.jar.md5 ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10-sources.jar ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10.jar.md5 ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10.pom.md5 ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10.pom ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10.jar ./jboss-eap-6.1.1.GA-maven-repository/org/jboss/as/jboss-as-client-all/7.2.1.Final-redhat-10/jboss-as-client-all-7.2.1.Final-redhat-10.jar.sha1
Hi Paul, it could be OK to remove the jar if there was a replacement for it. Is there any way for customers to get the correct dependencies without it?
For ER5 we will include the client-all jar again, and add a note to the documentation that this jar should not be used from the Maven repository. Either the ejb-client-bom or jms-client-bom should be used instead.
Added the jar to the manual include list: http://git.app.eng.bos.redhat.com/jboss-eap/maven-repository-testsuite.git/commit/?id=a0da1f123e6ec3e55478d81d9d09e384783e5e73
EAP 6.2.0 ER5 Maven repo zip contains jboss-as-client-all-7.3.0.Final-redhat-8.jar. Please make the note to the documentation before the jar is removed again so we can test it accordingly. I am setting this BZ verified and going to create a new one for the documentation.