qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-3024) Standardise Qpid concurrency utils by using classes from java.util.concurrent
Date Sun, 19 Feb 2012 17:26:36 GMT

     [ https://issues.apache.org/jira/browse/QPID-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robbie Gemmell resolved QPID-3024.

    Resolution: Fixed

Resolving this, the o.a.q.u.c package no longer exists, and the junit related ones will be
taken out along with the junit toolkit itself at a [hopefully not that much longer in the]
future date
> Standardise Qpid concurrency utils by using classes from java.util.concurrent
> -----------------------------------------------------------------------------
>                 Key: QPID-3024
>                 URL: https://issues.apache.org/jira/browse/QPID-3024
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Andrew Kennedy
>            Assignee: Andrew Kennedy
>            Priority: Minor
> The standard Java concurrency utility classes should be used wherever possible. This
should reduce maintenance and increase reliability by using only external, well tested implementations.
This would obsolete most of the classes in the org.apache.qpid.util.concurrent package, most
of which are never used anyway, as well as those from the org.apache.qpid.junit.concurrency

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


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message