You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2015/04/28 19:08:06 UTC

[jira] [Created] (QPID-6515) Eliminate dependencies that require commons-logging (beanutils and collections)

Lorenz Quack created QPID-6515:
----------------------------------

             Summary: Eliminate dependencies that require commons-logging (beanutils and collections)
                 Key: QPID-6515
                 URL: https://issues.apache.org/jira/browse/QPID-6515
             Project: Qpid
          Issue Type: Improvement
          Components: Java Broker, Java Performance Tests
            Reporter: Lorenz Quack
            Priority: Minor


Qpid perftests and JMX management plugin (tests) currently use Apache commons jars (beanutils and collections) that makes use of commons-logging.

Commons-logging adds unnecessary complication to the task of reimplementing logging within the Broker. It would be possible to use a JCL to SLF4J bridge - but this seem burdensome. It would be especially so when running the client and broker within a single JVM where it is likely we will want to rely on the fact that LogBack exposes a SLF4J compatible interface.

It will be simpler to remove the dependencies from the project.

Task is to reimplement the methods that make use of BidiMap, BeanUtils, PropertyUtils so these dependencies can be eliminated completely from the project.

For BidiMap, Guava has a BiMap which might be a drop in replacement. For BeanUtils/PropertyUtils we can reimplement from scratch or selectively bring in parts of the code from the Apache neighbouring projects.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org