DR4 results: 21 failures from 413
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/26/testReport/

EAP 6.1.0 ER1 -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/28/testReport/

14 failures to go

asm-3.3.1-redhat-2
jackson-core-asl-1.9.9-redhat-0-todo
jackson-jaxrs-1.9.9-redhat-0-todo
jackson-mapper-asl-1.9.9-redhat-0-todo
jackson-xc-1.9.9-redhat-0-todo
jacorb-2.3.2-redhat-1
jsf-api-1.2_15-b01-redhat-2
jsf-impl-1.2_15-b01-redhat-2
jsr181-api-1.0-MR1-redhat-2
not-yet-commons-ssl-0.3.11-redhat-2
stax2-api-3.1.1-redhat-2
woodstox-core-asl-4.1.1-redhat-2
wsdl4j-1.6.2-redhat-2
xml-resolver-1.2-redhat-2

EAP 6.1.0 ER status 

infinispan-parent-5.2.1.Final-redhat-1
jackson-core-asl-1.9.9-redhat-1
jackson-jaxrs-1.9.9-redhat-1
jackson-mapper-asl-1.9.9-redhat-1
jackson-xc-1.9.9-redhat-1
asm-3.3.1-redhat-2
jsf-api-1.2_15-b01-redhat-2
jsf-impl-1.2_15-b01-redhat-2
jsr181-api-1.0-MR1-redhat-2
not-yet-commons-ssl-0.3.11-redhat-2
stax2-api-3.1.1-redhat-2
woodstox-core-asl-4.1.1-redhat-2
wsdl4j-1.6.2-redhat-2
xml-resolver-1.2-redhat-2

Jacorb pom file was fixed, new problem with infinispan-parent

EAP 6.1.0 ER3:

The same as above + infinispan-parent changed to 5.2.5.Final-redhat-1


https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/30/testReport/

EAP 6.1.0 ER4

redhat-2 changed to redhat-3, but not fixed. 
  asm-3.3.1-redhat-3
  wsdl4j-1.6.2-redhat-3

The rest without any change from EAP 6.1.0 ER3

EAP 6.1.0 ER5 - 7 failures
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/32/testReport/

relaxngDatatype-2011.1-redhat-5
asm-3.3.1-redhat-3
wsdl4j-1.6.2-redhat-3
infinispan-parent-5.2.5.Final-redhat-1
jsf-api-1.2_15-b01-redhat-2
jsf-impl-1.2_15-b01-redhat-2
xml-resolver-1.2-redhat-2

EAP 6.1.0 ER6 - 1 failure

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/35/testReport/
infinispan-parent-5.2.5.Final-redhat-1

The same results in EAP 6.1.0 ER8 as in ER6.

Marking this as rejected for 6.1.1.  If there are specific POMs that are causing problems for certain use cases, then we can address those in separate issues.

There are 3 failures in EAP 6.1.1 ER4:

jcip-annotations-1.0-redhat-4
infinispan-parent-5.2.7.Final-redhat-1
xml-resolver-1.2-redhat-2

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/45/testReport/

Results in EAP 6.1.1 ER6 are the same as in ER4.

1 new failure in EAP 6.1.1 ER7 -- commons-httpclient-3.1-jbossorg-1

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/50/testReport/

4 failures for EAP 6.2.0 ER6:

jsr181-api-1.0-MR1-redhat-4
commons-httpclient-3.1-jbossorg-1
infinispan-parent-5.2.7.Final-redhat-1
xml-resolver-1.2-redhat-2

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/61/testReport/

* jsr181-api-1.0-MR1-redhat-4 fixed within blocking bugzilla #1026827
* commons-httpclient-3.1-jbossorg-1 is upstream artifact, it's kept as it is
* infinispan-parent-5.2.7.Final-redhat-1 fixed within blocking bugzilla #1026839
* xml-resolver-1.2-redhat-2 was transitive dependency of hibernate quickstart and it was fixed in xml-resolver-1.2.redhat-9

Verified on EAP 6.2.0 CR1

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files/65/testReport/

Only one fail for commons-httpclient-3.1-jbossorg-1 which is importd from upstream, commons-httpclient-3.1-redhat-3 has correct format.

BZ for duplicated commons-httpclient artifact was filled weeks ago.