Do we have a commitment from ActiveMQ to remove its backport-util-concurrent usage in a 4.1 release for our 2.0 release?

-Donald

Jason Dillon (JIRA) wrote:
     [ 
https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon closed GERONIMO-2995.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta1

This is done, once AMQ removes dependency on this... then we can get it out of 
the repository.

Weed out backport-util-concurrent usage for server/trunk
--------------------------------------------------------

                Key: GERONIMO-2995
                URL: https://issues.apache.org/jira/browse/GERONIMO-2995
            Project: Geronimo
         Issue Type: Improvement
Security Level: public(Regular issues) Affects Versions: 2.0
           Reporter: Jason Dillon
        Assigned To: Jason Dillon
            Fix For: 2.0-beta1


Now that server/trunk requires 1.5 to build and run, I think we should start to 
weed out our usage of the {{backport-util-concurrent}} library (and concurrent 
if there is still anything left of that in our src tree).
I think we may still have to include {{backport-util-concurrent-\*.jar}} in the 
assembly until all of our dependencies have weeded it out too... or perhaps 
just have to live with that in the repository.  But hopefully we can remove our 
usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations 
(based on imports) which are over 25 files.
Even after weeding out *our* usage, if we still need to include this jar I 
recommend we update to the latest release 3.0.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to