Bug 1017619 - Maven repo zip contains supported artifacts with invalid OSGi version
Maven repo zip contains supported artifacts with invalid OSGi version
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Maven Repository (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ER3
: EAP 6.4.0
Assigned To: Paul Gier
Nikoleta Ziakova
Depends On:
Blocks: 1120790
  Show dependency treegraph
Reported: 2013-10-10 05:00 EDT by Nikoleta Ziakova
Modified: 2017-10-09 20:24 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nikoleta Ziakova 2013-10-10 05:00:13 EDT
There are 217 artifacts that do not meet the OSGi requirements in EAP 6.2.0 ER5 Maven repo zip. 

For full list of these artifacts see:
Comment 2 Kabir Khan 2014-11-13 17:50:07 EST
AFAIK we OSGi is in tech preview, but I will test https://github.com/jbossas/jboss-eap/pull/1961 for merge anyway
Comment 3 Nikoleta Ziakova 2014-11-21 06:44:12 EST
There are still 107 failures in EAP 6.4.0.DR10 Maven repo zip, see:
Comment 4 Kabir Khan 2014-12-03 05:12:44 EST
Comment 5 Lin Gao 2014-12-05 02:28:29 EST
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?
Comment 6 Nikoleta Ziakova 2014-12-10 09:35:12 EST
70 failures in EAP 6.4.0.DR13, see:

I can confirm that all artifacts from PR in comment 5 have now valid version.
Comment 10 Paul Gier 2014-12-16 16:52:53 EST
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.
Comment 12 Kabir Khan 2014-12-22 08:01:10 EST
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
Comment 13 Nikoleta Ziakova 2015-01-06 08:34:29 EST
List of affected jars for EAP 6.4.0.DR13 can be found here:

Total invalid versions: 70
Invalid versions affecting JAR artifacts only: 24
Comment 16 Paul Gier 2015-01-09 15:31:25 EST
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.
Comment 18 Kabir Khan 2015-01-14 11:52:21 EST
Comment 19 Kabir Khan 2015-01-14 11:53:48 EST
Also https://github.com/jbossas/jboss-eap/pull/2231
Comment 20 Kabir Khan 2015-01-15 15:00:33 EST
and https://github.com/jbossas/jboss-eap/pull/2237
Comment 21 Lin Gao 2015-01-15 21:38:53 EST
And hopefully the last PR: https://github.com/jbossas/jboss-eap/pull/2245
Comment 24 Paul Gier 2015-02-10 17:15:12 EST
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 

jaxb-api-2.1.4                       This version is valid OSGi
                                     Not sure why this was in test output
Comment 25 Paul Gier 2015-02-10 17:22:55 EST
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.
Comment 31 Paul Gier 2015-03-10 09:44:24 EDT
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.
Comment 33 Nikoleta Ziakova 2015-03-12 04:15:36 EDT
Verified using EAP 6.4.0.ER3 bits: all EAP supported artifacts have valid OSGi version.

Note You need to log in before you can comment on or make changes to this bug.