171 failures in 6.3.0 ER1:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-valid-versions/94/testReport/

AFAIK we OSGi is in tech preview, but I will test https://github.com/jbossas/jboss-eap/pull/1961 for merge anyway

There are still 107 failures in EAP 6.4.0.DR10 Maven repo zip, see:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-6x-repository-maven-check-valid-osgi-versions/115/testReport/

https://github.com/jbossas/jboss-eap/pull/2105

Second PR: https://github.com/jbossas/jboss-eap/pull/2125

There will be more components rebuilding coming soon. Maybe we can keep it as POST status for PR reference?

70 failures in EAP 6.4.0.DR13, see:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-repository-maven-check-valid-osgi-versions/123/testReport/

I can confirm that all artifacts from PR in comment 5 have now valid version.

Nikoleta,  can you update the test to provide results that look only at versions which affect a jar or zip file?  Many of the failures are POM only artifacts which could be difficult to remove from the repo without breaking dependency resolution, and should not have any effect on OSGi behaviour afaik.

Some of the other failures are related to unsupported artifacts which are used only for dependency resolution, and we'll work on fixing these by ER1 or ER2.

I have merged https://github.com/jbossas/jboss-eap/pull/2174 but am unclear if that fixes everything or not. Still I have set to MODFIED, Paul please correct if that is a problem

List of affected jars for EAP 6.4.0.DR13 can be found here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-repository-maven-check-valid-osgi-versions/124/artifact/invalid-versions-jars.txt

Total invalid versions: 70
Invalid versions affecting JAR artifacts only: 24

There are still a few more jars to merge, but it would be good to get updated test results to verify the remaining jars.  Plan to have this resolved for the next build.

There are 19 failures affecting JARs in EAP 6.4.0.ER1:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-repository-maven-check-valid-osgi-versions/126/artifact/invalid-versions-jars.txt

https://github.com/jbossas/jboss-eap/pull/2228

Also https://github.com/jbossas/jboss-eap/pull/2231

and https://github.com/jbossas/jboss-eap/pull/2237

And hopefully the last PR: https://github.com/jbossas/jboss-eap/pull/2245

There are still 12 failures affecting JARs in EAP 6.4.0.ER2:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-6x-repository-maven-check-valid-osgi-versions/127/artifact/invalid-versions-jars.txt

Jenkins Invalid Versions             Notes
------------------------             ------

commons-lang-2.6-redhat-2            Supported version is 2.6.0.redhat-4
                                     Older version contained in old BOM

icu4j-49.1-redhat-1                  Not supported, transitive dep of lucene-icu

guava-13.0.1-redhat-1                Supported version is 13.0.1.redhat-2
                                     Old version is transitive dep of lucene

relaxngDatatype-2011.1-redhat-3      Supported version is 2011.1.0.redhat-9
                                     Older version contained in old BOM

commons-io-2.1-redhat-2              Supported version is 2.1.0.redhat-4
                                     Older version contained in old BOM

mimepull-1.2-redhat-2                Artifact is not supported
                                     Older version contained in old BOM

rhq-pluginAnnotations-3.0.4-redhat-2 Not supported, transitive dep 
                                     of remoting-jmx 1.1.3.Final-redhat-2

weld-spi-1.1.Final-redhat-5          Supported version is 1.1.0.Final-redhat-6

weld-api-1.1.Final-redhat-5          Supported version is 1.1.0.Final-redhat-6

jboss-el-1.0_02.CR5                  Unsupported, transitive dep of jboss-seam

javassist-3.18.1-GA-redhat-1         Supported version is 3.18.1.GA-redhat-1
                                     Transitive dep of remoting-jmx and 
                                     hibernate.

jaxb-api-2.1.4                       This version is valid OSGi
                                     Not sure why this was in test output

None of the remaining invalid versions are supported jars, and therefore would not be accessed when using the appropriate Maven dependency management with a BOM, so I don't consider this to be a blocker anymore.

The current build of remoting-jmx (1.1.3.Final-redhat-2), hibernate (4.2.18.Final-redhat-1), and lucene (3.6.2.redhat-7) are the cause of several of these issues because their poms directly reference the older transitive dependencies.

I propose that we look at updating/rebuilding these three, and ignore the other cases.

Created a new issue for the remaining non-blocking artifacts (bug #1017619).
Moving this issue back to ON_QA so the blocker portion of this issue can be closed.

Verified using EAP 6.4.0.ER3 bits: all EAP supported artifacts have valid OSGi version.