camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (Created) (JIRA) <j...@apache.org>
Subject [jira] [Created] (CAMEL-4623) Upgrade commons-pool:commons-pool 1.5.4 -> 1.5.6
Date Sat, 05 Nov 2011 14:32:51 GMT
Upgrade commons-pool:commons-pool 1.5.4 -> 1.5.6
------------------------------------------------

                 Key: CAMEL-4623
                 URL: https://issues.apache.org/jira/browse/CAMEL-4623
             Project: Camel
          Issue Type: Task
            Reporter: Christian Müller
            Assignee: Christian Müller
            Priority: Minor


>From commons-pool 1.5.4 to 1.5.6 they fixed 13 bugs:

[commons-pool 1.5.5 release notes|https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310488&version=12314491]
[commons-pool 1.5.6 release notes|https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310488&version=12316032]

I'm wondering whether we still need a bundle from the SMX guys, because they removed the "Import-Package"
definition in the MANIFEST.MF file, which was the reason for the SMX bundle when I remember
right.
But there is still a difference. The SMX bundle includes the uses:="" definition in the Export-Package
definition which the commons-pool-1.5.6 doesn't use.
Could an OSGI expert (JB?) tell me if this is a problem?

commons-pool-1.5.4.jar:
{noformat}
Export-Package: org.apache.commons.pool.impl;version="1.5.4",org.apach
 e.commons.pool;version="1.5.4"
Import-Package: org.apache.commons.pool;version="1.5.4",org.apache.com
 mons.pool.impl;version="1.5.4"
{noformat}

org.apache.servicemix.bundles.commons-pool-1.5.4_3.jar:
{noformat}
Export-Package: org.apache.commons.pool.impl;uses:="org.apache.commons
 .pool";version="1.5.4",org.apache.commons.pool;version="1.5.4"
{noformat}

commons-pool-1.5.6.jar:
{noformat}
Export-Package: org.apache.commons.pool.impl;version="1.5.6",org.apach
 e.commons.pool;version="1.5.6"
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message