Bug 1093401
| Summary: | Mulitple jar versions in modeshape-cmis WAR | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Julian Coleman <jcoleman> |
| Component: | Productization | Assignee: | Jan <jschatte> |
| Status: | CLOSED WONTFIX | QA Contact: | Jan Stastny <jstastny> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0, 6.1.0 | CC: | atangrin, drieden, felias, hchiorea, jstastny, vhalbert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-05-15 14:40:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Julian Coleman
2014-05-01 15:42:12 UTC
In DV 6.1 ER2, this is still an issue with the following jar's: activation-1.1.1-redhat-2.jar and activation-1.1.jar jaxb -impl-2.1.11.jar and jaxb-impl-2.2.5.redhat-8.jar saaj-imple-1.3.3.jar and saaj-impl-1.3.16.redhat-3.jar stax2-api-3.1.1.jar and stax2-api-3.1.3.redhat-1.jar woodstox-core-asl-4.2.0.jar and woodstox-core-asl-4.2.0.redhat-4.jar @julian: some of these jars (if not all) are coming from the local ModeShape build and it's something I hope to fix for ER3. The duplicate JARs that are coming from the local build which I will fix for ER3 are: activation-*, jaxb-api-*, jaxb-impl-*. The rest are most likely coming during the productization process and will have to be fixed accordingly. ER3 still has duplicates for stax-api, stax2-api and woodstox-core-asl jar's. Building locally the 3.8.x-prod-ip6.1-ER3-2 tag (which is what should've been used for ER3) produces a WAR with the following JARs in the lib: activation-1.1.1.jar antlr-2.7.7.jar antlr-runtime-3.5.jar chemistry-opencmis-commons-api-0.11.0.jar chemistry-opencmis-commons-impl-0.11.0.jar chemistry-opencmis-server-bindings-0.11.0.jar chemistry-opencmis-server-bindings-war-0.11.0.jar chemistry-opencmis-server-jcr-0.11.0-classes.jar chemistry-opencmis-server-support-0.11.0.jar commons-collections-3.2.1.jar commons-lang-2.6.jar jaxb-api-2.2.5.jar jaxb-impl-2.2.5.jar jaxws-api-2.1.jar jaxws-rt-2.1.7.jar mimepull-1.9.4.jar modeshape-web-cmis-3.8.1.GA.jar modeshape-web-jcr-3.8.1.GA.jar resolver-20050927.jar slf4j-api-1.7.5.jar stax-api-1.0-2.jar stax-ex-1.2.jar stax2-api-3.1.1.jar streambuffer-0.9.jar stringtemplate-3.2.1.jar woodstox-core-asl-4.2.0.jar So either this tag wasn't used or something got messed up during the productization build. Had a look at the Maven repo for ER3 and the tag used to build ModeShape is correct (id: 6f363abe2e3fd69bfc606da116908db936de4b55). So something must've gotten messed up when building the WAR files that are packaged inside the ModeShape EAP kit, namely: modeshape-jbossas-cmis-war Fixed with commit 9cfc2d3c5b3a0c0bc9cd11b989b4e9e63b94a816 to rpms/modeshape.git:
BZ-1093401
Add patch to exclude community jars from the CMIS war where we have multiple
versions present.
ER6 has duplicates for stax-api: stax-api-1.0-2.jar stax-api-1.0.jar The list of transitive dependencies of this module looks like this: INFO] +- javax.jcr:jcr:jar:2.0:provided INFO] +- org.modeshape:modeshape-common:jar:3.8.2.GA:provided INFO] +- org.modeshape:modeshape-jcr-api:jar:3.8.2.GA:provided INFO] +- org.modeshape:modeshape-web-cmis:jar:3.8.2.GA:compile INFO] | +- org.modeshape:modeshape-web-jcr:jar:3.8.2.GA:compile INFO] | +- org.apache.chemistry.opencmis:chemistry-opencmis-commons-api:jar:0.11.0:compile INFO] | | \- org.slf4j:slf4j-api:jar:1.7.2:test INFO] | +- org.apache.chemistry.opencmis:chemistry-opencmis-commons-impl:jar:0.11.0:compile INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile INFO] | | | +- javax.xml.stream:stax-api:jar:1.0-2:compile INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile INFO] | | +- org.jvnet.mimepull:mimepull:jar:1.9.4:compile INFO] | | \- com.sun.xml.ws:jaxws-rt:jar:2.1.7:compile INFO] | | +- javax.xml.ws:jaxws-api:jar:2.1:compile INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.5:compile INFO] | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.5:compile INFO] | | +- com.sun.xml.stream.buffer:streambuffer:jar:0.9:compile INFO] | | | \- javax.activation:activation:jar:1.1.1:compile INFO] | | +- org.jvnet.staxex:stax-ex:jar:1.2:compile INFO] | | \- com.sun.org.apache.xml.internal:resolver:jar:20050927:compile INFO] | +- org.apache.chemistry.opencmis:chemistry-opencmis-server-support:jar:0.11.0:compile INFO] | | \- org.antlr:antlr-runtime:jar:3.2:test INFO] | | \- org.antlr:stringtemplate:jar:3.2:test INFO] | | \- antlr:antlr:jar:2.7.7:test INFO] | \- org.apache.chemistry.opencmis:chemistry-opencmis-server-jcr:jar:classes:0.11.0:compile INFO] | +- org.apache.chemistry.opencmis:chemistry-opencmis-server-bindings-war:war:0.11.0:compile INFO] | \- commons-collections:commons-collections:jar:3.2.1:compile INFO] \- com.h2database:h2:jar:1.3.168:test The other JARs come from overlaying org.apache.chemistry.opencmis:chemistry-opencmis-server-bindings-war:0.11.0:war (which is the version coming from the BOM)and these only include stax-api-1.0-2.jar This is consistent with what I'm seeing when building modeshape-jbossas-cmis-war-3.8.2.GA.war locally - i.e. I don't see the duplicate JARs in the WAR that's being built locally. So atm. I have absolutely no idea where stax-api-1.0.jar could be coming from. |