qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6515) Eliminate dependencies that require commons-logging (beanutils and collections)
Date Tue, 28 Apr 2015 17:18:06 GMT

    [ https://issues.apache.org/jira/browse/QPID-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517448#comment-14517448
] 

ASF subversion and git services commented on QPID-6515:
-------------------------------------------------------

Commit 1676579 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1676579 ]

QPID-6515 : [Java Broker, Java Performance Tests] Eliminate dependencies that require commons-logging
(patch by Lorenz Quack)

> 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
>         Attachments: 0001-QPID-6515-Java-Broker-Java-Performance-Tests-Elimina.patch
>
>
> 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


Mime
View raw message