Bug 900859 (JBPAPP6-1121) - Upgrade apache-mime4j to 0.7.2
Summary: Upgrade apache-mime4j to 0.7.2
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBPAPP6-1121
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Build
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 6.0.1
Assignee: Yong Yang
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks: JBPAPP6-1082 JBPAPP6-1095
TreeView+ depends on / blocked
 
Reported: 2012-09-07 07:55 UTC by Yong Yang
Modified: 2014-06-28 12:47 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-08 09:09:48 UTC
Type: Task
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP6-1121 0 Major Closed Upgrade apache-mime4j to 0.7.2 2015-05-06 15:07:13 UTC

Description Yong Yang 2012-09-07 07:55:36 UTC
project_key: JBPAPP6

The version of apache-mime4j needed by EAP6.0.1(AS7.1.3) is 0.6, while apache-cxf 2.4.8-patch-01 needs 0.7.2. (apache-cxf 2.4.8-patch-01 -> ws-commons-neethi 3.0.2 -> ws-commons-axiom 1.2.13 -> apache-mime4j 0.7.2)

apache-mime4j 0.7.2 has significant updates since 0.6, new classes, new APIs, even the artifactIds are changed, it's not compatible with 0.6. Downgrading apache-mime4j to 0.6 for apache-cxf is difficult.

So to avoid multiple versions of apache-mime4j being used in EAP 6.0.1, need to upgrade the dependency of apache-mime4j to 0.7.2 in EAP 6.0.1.

Comment 2 Yong Yang 2012-09-10 08:05:14 UTC
Weinan, please confirm if resteasy can use apache-mime4j-core 0.7.2-redhat-2? thanks.

[INFO] |  +- org.jboss.resteasy:resteasy-multipart-provider:jar:2.3.4.Final-redhat-2:provided
[INFO] |  |  \- org.apache.james:apache-mime4j:jar:0.6-redhat-2:provided

Comment 3 Weinan Li 2012-09-10 09:17:52 UTC
the local build passed after mime4j upgraded but mead build failed. I'll try to investigate more on this.

Comment 5 Fernando Nasser 2012-09-13 20:55:39 UTC
We reverted to ws-commons-neethi 3.0.1  and tests indicate no regression
(thanks to QE for checking that).

We also removed the dependency on axiom from neethi so if we need
to upgrade neethi to 3.0.2 we can do so without having to upgrade
mime4j 0.7 (that was a requirement of axiom, not neethi directly).

RESTEasy trunk has moved over, the AS master may eventually move over as well, so probably 6.1 will have the new mime4j 0.7.


Comment 6 Paul Gier 2012-09-24 17:22:56 UTC
Link: Added: This issue depends AS7-5623


Comment 7 Paul Gier 2012-09-24 17:35:03 UTC
Link: Added: This issue is a dependency of JBPAPP-9721


Comment 8 Paul Gier 2012-09-24 17:37:56 UTC
We need to upgrade neethi to 3.0.2 because that's what the upstream 7.1 branch (and 7.1.3.Final tag) is using.  I created JBPAPP-10009 to track the Neethi upgrade.

Comment 9 Fernando Nasser 2012-09-24 19:11:27 UTC
This requires a new package as we need to keep the old version around (it is shipped and used by other components).  Yang, pls contact me for how to handle this.

Comment 10 Fernando Nasser 2012-09-24 19:32:53 UTC
Link: Added: This issue is a dependency of JBPAPP-10009


Comment 11 Fernando Nasser 2012-09-25 12:19:33 UTC
This was needed (indirectly) to upgrade neethi but Yang has worked around that requirements.

Comment 12 Rostislav Svoboda 2012-10-30 11:34:46 UTC
closing, marked as won't fix

Comment 13 Misty Stanley-Jones 2012-11-05 05:18:28 UTC
Release Notes Docs Status: Added: Not Required


Comment 14 Anne-Louise Tangring 2012-11-13 20:28:11 UTC
Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW 



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