Same issue was fixed for EAP 6.1.1

There are still problem with EAP 6.2.0 ER3.1 maven repo zip.

For example: 
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact com.sun:tools:jar:1.6

A. This will be fixed in the next release.

B. The dependencies com.sun:tools and sun.jdk:jconsole have been excluded for the next build
http://git.app.eng.bos.redhat.com/?p=jboss-eap/maven-repository-testsuite.git;a=commitdiff;h=d27b9c75ee5ad56a0b7ddde59412fc0abd353891

I don't agree that we should define types in the POM (org.jboss.hal:release-stream and org.jboss.ws.cxf:jbossws-cxf-resources).  It's up to the user to define which type of artifact they want to download, the BOM only defines the versions.

C. This will be fixed in the next release.

Built with ER4.

3 artefacts still unavailable in EAP 6.2.0 ER4 Maven repo zip:

(B) missing dependencies:
    org.jboss.ws.cxf:jbossws-cxf-resources:jar:4.2.1.Final-redhat-3
    (zip contains jbossws-cxf-resources-4.2.1.Final-redhat-3-jboss720.jar)

    org.jboss.hal:release-stream:jar:2.0.2.Final-redhat-1
    (zip contains release-stream-2.0.2.Final-redhat-1-resources.jar)

(C) missing transitive dependencies:
    junit:junit:jar:4.10-redhat-2 
    (dependency of org.jboss.com.sun.httpserver:httpserver:jar:1.0.1.Final-redhat-2)

Note for (B):
These artifacts have classifier. For resolving them using <classifier/> is mandatory i.e.

<dependency>
  <artifactId>org.jboss.ws.cxf</artifactId>
  <groupId>jbossws-cxf-resources</groupId>
  <classifier>jboss720</classifier>
  ...
</dependency>

<dependency>
  <artifactId>org.jboss.hal</artifactId>
  <groupId>release-stream</groupId>
  <classifier>resources</classifier>
  ...
</dependency>

Note for (C):
Junit is a transitive dependency but just for testing purposes. Could be excluded in dependency to httpserver (but it's workaround). Better solution is to rebuild httpserver with dependency on upstream junit, then this transitivity will be solved trivially with using central to resolve junit. The second option is to include additional artifact junit:junit:jar:4.10-redhat-2 into the Maven repository zip (temporary until httpserver is rebuilt with upstream junit).

Comment regarding (C): As Vladimir suggested, this should be changed to the upstream version to make it clear that JUnit is not a supported jar.  In addition, it might be good to change the dependency scope to "test" or make the dependency optional, because JUnit should not be required to use use the httpserver jar from the Maven repo.

For (C), httpserver rebuilt, PR for EAP sent, see blocking BZ 1016048.

New build of httpserver will not bring in transitive junit dependency.

(B) artifacts with classifier

I added classifiers into the test pom. However these artifacts can not be resolved becase their version is not defined.

For example for dependency org.jboss.ws.cxf:jbossws-cxf-resources:jar:jboss720 I get the following error:

[ERROR] 'dependencies.dependency.version' for org.jboss.ws.cxf:jbossws-cxf-resources:jar:jboss720 is missing. @ line 337, column 14

The same problem is for missing type definition when artifact is not of type 'jar'.

(C) transitive dependencies

After defining classifier and version for org.jboss.hal:release-stream:jar:2.0.2.Final-redhat-1 I found another issue, this artifact is missing a dependency:

org.jboss.as:jboss-as-console-resources:war:2.0.3.Final-redhat-2

Current issues with the BOM in EAP 6.2.0 ER5:

(B) missing dependencies:

    org.jboss.as:jboss-as-build:jar:7.3.0.Final-redhat-8
    (type pom not defined)

    org.jboss.hal:release-stream:jar:2.0.3.Final-redhat-1
    (classifier not defined)

    org.jboss.ws.cxf:jbossws-cxf-resources:jar:4.2.1.Final-redhat-3
    (classifier not defined)

(C) missing transitive dependencies:

    org.apache.cxf:cxf-rt-transports-udp:jar:2.7.6.redhat-2
    (dependency of org.apache.cxf.services.ws-discovery:cxf-services-ws-discovery-api:jar:2.7.6.redhat-2)

    org.jboss.as:jboss-as-console-resources:war:2.0.3.Final-redhat-2
    (dependency of org.jboss.hal:release-stream:jar:resources:2.0.3.Final-redhat-1)

Added the two missing transitive dependencies:
http://git.app.eng.bos.redhat.com/jboss-eap/maven-repository-testsuite.git/commit/?id=3b755ef1a0a0c7da609fe974e43117721fdbc6d4

Fixed in the ER5.1 maven repo.

Verified for EAP 6.2.0 ER5.1

This issue was fixed in EAP 6.2.0 ER5.1. However there is another issue in EAP 6.2.0 ER6 so I am repoening this.

One new missing transitive dependency:

org.jboss.jbossts:jbossjts:jar:4.16.6.Final-redhat-1
(is a dependency of org.hornetq:hornetq-jms-server:jar:2.3.9.Final-redhat-1)

HornetQ should be rebuilt with latest jbossts in the next release to use the same version of jbossts as AS/EAP parent/build pom.

It seems jbossts is the test scoped dependency of hornetq but hornetq doesn't specify it in its pom as test scoped. HornetQ poms should be checked and test/optional dependencies should be set with the proper scope.

HornetQ was using the 4.16.x version of jbossts which used the older groupId/artifactId.  This should be resolved in the next version of hornetq included in ER7 (https://issues.jboss.org/browse/HORNETQ-1269).

3 missing transitive dependencies in EAP 6.2.0 ER7:

org.apache.cxf:cxf-rt-javascript:jar:2.7.7.redhat-1
    dependency of: org.apache.cxf:cxf-tools-java2ws:jar:2.7.7.redhat-1
    version available in Maven repo zip: 2.7.6.redhat-2

org.apache.cxf:cxf-rt-transports-udp:jar:2.7.7.redhat-1
    dependency of: org.apache.cxf.services.ws-discovery:cxf-services-ws-discovery-api:jar:2.7.7.redhat-1
    version available in Maven repo zip: 2.7.6.redhat-2

org.jboss.as:jboss-as-console-resources:war:2.0.5.Final-redhat-1
    dependency of: org.jboss.hal:release-stream:jar:resources:2.0.5.Final-redhat-1
    version available in Maven repo zip: 2.0.3.Final-redhat-2

Note for the 3rd missing dependency in my comment #27:

Maven repo zip contains BOM org.jboss.as:jboss-as-console-bom:2.0.3.Final-redhat-2, but it should be the version 2.0.5.Final-redhat-1

Fixed in
 * http://git.app.eng.bos.redhat.com/jboss-eap/maven-repository-testsuite.git/commit/?id=9ee5f88c5e5b98bdc1044dc419214af80521f52f
 * http://git.app.eng.bos.redhat.com/jboss-eap/maven-repository-testsuite.git/commit/?id=ec7118839547a95bc60b24c12e5bf76e9aa135d1

org.jboss.as:jboss-as-console-resources:war:2.0.5.Final-redhat-1 is still missing. Neither 2.0.5.Final-redhat-1, nor 2.0.3.Final-redhat-2 is available in EAP 6.2.0 ER7.1 Maven repo zip.

One new missing dependency:
org.jboss.jdeparser:jdeparser:jar:1.0.0.Final-redhat-1
    is dependency of: org.jboss.osgi.metadata:jbosgi-metadata:jar:2.2.0.Final-redhat-1
    no version of this artifat available in ER7.1 but it was available in ER7

Added a manual include for jdeparser:
http://git.app.eng.bos.redhat.com/jboss-eap/maven-repository-testsuite.git/commit/?id=94e57bded6b04a432399284a32d7fd2e85cd8567

The console resources war file was missing because of a change in our repo gen tool, which is now fixed.

Verified for EAP 6.2.0 ER7.2

All artifacts referenced in eap6-supported-artifacts BOM are available either in Maven repository zip or in central repository.

NOTE: central repository must be enabled to get all the artifacts.