You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2010/02/02 22:05:32 UTC

[jira] Created: (AMQ-2592) Upgrade to commons-pool 1.5.4

Upgrade to commons-pool 1.5.4
-----------------------------

                 Key: AMQ-2592
                 URL: https://issues.apache.org/activemq/browse/AMQ-2592
             Project: ActiveMQ
          Issue Type: Task
    Affects Versions: 5.3.0
            Reporter: Gert Vanthienen
            Priority: Minor
             Fix For: 5.3.1
         Attachments: AMQ-2592.diff

In Camel 2.2.0, the version of commons-pool is upgraded from 1.4 to 1.5.4.  Whenever we include that version in ActiveMQ, we would have to make the same upgrade to avoid running into version resolution problems when combining the two of them in an OSGi environment (e.g. ServiceMIx).

The patch only contains the trivial pom change - I did run a full build and that didn't reveal any issues with this upgrade.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQ-2592) Upgrade to commons-pool 1.5.4

Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gert Vanthienen updated AMQ-2592:
---------------------------------

    Attachment: AMQ-2592.diff

> Upgrade to commons-pool 1.5.4
> -----------------------------
>
>                 Key: AMQ-2592
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2592
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.3.0
>            Reporter: Gert Vanthienen
>            Priority: Minor
>             Fix For: 5.3.1
>
>         Attachments: AMQ-2592.diff
>
>
> In Camel 2.2.0, the version of commons-pool is upgraded from 1.4 to 1.5.4.  Whenever we include that version in ActiveMQ, we would have to make the same upgrade to avoid running into version resolution problems when combining the two of them in an OSGi environment (e.g. ServiceMIx).
> The patch only contains the trivial pom change - I did run a full build and that didn't reveal any issues with this upgrade.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AMQ-2592) Upgrade to commons-pool 1.5.4

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies resolved AMQ-2592.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.4.0
         Assignee: Rob Davies

 Updated in SVN revision 906094 for 5.4 and 906096 for 5.3

> Upgrade to commons-pool 1.5.4
> -----------------------------
>
>                 Key: AMQ-2592
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2592
>             Project: ActiveMQ
>          Issue Type: Task
>    Affects Versions: 5.3.0
>            Reporter: Gert Vanthienen
>            Assignee: Rob Davies
>            Priority: Minor
>             Fix For: 5.3.1, 5.4.0
>
>         Attachments: AMQ-2592.diff
>
>
> In Camel 2.2.0, the version of commons-pool is upgraded from 1.4 to 1.5.4.  Whenever we include that version in ActiveMQ, we would have to make the same upgrade to avoid running into version resolution problems when combining the two of them in an OSGi environment (e.g. ServiceMIx).
> The patch only contains the trivial pom change - I did run a full build and that didn't reveal any issues with this upgrade.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.