|Summary:||(6.3.z) Invalid OSGi artifact versions affecting Layered Platforms|
|Product:||[JBoss] JBoss Enterprise Application Platform 6||Reporter:||kconner|
|Component:||Maven Repository||Assignee:||Paul Gier <pgier>|
|Status:||CLOSED WONTFIX||QA Contact:||Nikoleta Hlavickova <nziakova>|
|Version:||6.3.0||CC:||asantos, bsutter, cdewolf, chaowan, dpospisi, jawilson, jdoyle, kconner, myarboro, ncross, sbunciak, vhalbert|
|Target Release:||EAP 6.3.3|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2015-01-22 10:49:52 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1017619|
|Bug Blocks:||1118675, 1151405|
Description kconner 2014-07-17 17:10:04 UTC
Discussion on the Wolf mailing list has highlighted a number of EAP artifacts that are being generated with invalid OSGi versions, a subset of which causes issues for FSW because they prevent us from installing into an OSGi environment and lead to failures such as Error executing command: invalid version "1.6.2-redhat-4": non-numeric "2-redhat-4" (in this instance caused by joda-time) This is blocking FSW work on Fuse, the primary reason for our 6.1 release, as we are unable to install features using productised versions of those artifacts. At this stage there appears to be 22 productised artifacts that we are currently pulling in from the EAP distribution or maven repository. The list of artifacts, versions and their paths (location when install in fuse, location in the EAP distribution and/or location in EAP maven repository) is attached.
Comment 1 kconner 2014-07-17 17:10:33 UTC
Created attachment 918785 [details] List of problematic artifacts
Comment 3 Paul Gier 2014-07-22 20:14:00 UTC
This is something we have been working to fix over the last few releases. It should be fully resolved in 6.4. We can address specific problematic artifacts in the 6.3 patch stream if necessary.
Comment 4 kconner 2014-07-28 19:24:51 UTC
All the problematic artifacts are in the attachment, these affect the current FSW build.
Comment 7 Dominik Pospisil 2014-11-19 12:52:13 UTC
Comment 8 Paul Gier 2014-11-20 14:31:20 UTC
staxmapper (1.1.0.Final) and jbossws-api (1.0.0.GA) appear to have valid OSGi versions. Can you describe why these were included in the list?
Comment 11 Nikoleta Hlavickova 2015-01-19 09:53:00 UTC
I can still see some of the problematic artifacts (from comment 1) in EAP 6.3.3.CP.CR1: txw2-20110809-redhat-4 relaxngDatatype-2011.1-redhat-6 commons-cli-1.2.redhat-4 commons-lang-2.6.redhat-3 commons-io-2.1.redhat-3 joda-time-1.6.2-redhat-4 commons-codec-1.4.redhat-3 commons-configuration-1.6.redhat-3 jcip-annotations-1.0.redhat-6 mail-1.4.5-redhat-1 activation-1.1.1-redhat-2 commons-pool-1.6.redhat-6 apache-mime4j-0.6.redhat-3 snakeyaml-1.8-redhat-2 javassist-3.18.1-GA-redhat-1 commons-httpclient-3.1-jbossorg-1 For all invalid version affecting JAR artifacts see test results (please note the test run on the incremental Maven repository including also EAP 6.3.0.GA artifacts): https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP-6.3.x-CP/view/EAP-6.3.x-CP-jobs/job/eap-63x-patched-repository-maven-check-valid-osgi-versions/8/artifact/invalid-versions-jars.txt