[jira] [Created] (UIMA-2713) Modify DUCC's assembly script to filter out slf4j from spring and amq

["Jerry Cwiklik (JIRA)" <de...@uima.apache.org>]

Jerry Cwiklik created UIMA-2713:
-----------------------------------

             Summary: Modify DUCC's assembly script to filter out slf4j from spring and amq
                 Key: UIMA-2713
                 URL: https://issues.apache.org/jira/browse/UIMA-2713
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
            Priority: Minor


Both AMQ and Spring ship with their own version of slf4j jars. At runtime, the following message is dumped:

SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/home/challngr/ducc_runtime/lib/slf4j/slf4j-log4j12.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/challngr/ducc_runtime/lib/springframework/slf4j-log4j12-1.5.11.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/challngr/ducc_runtime/lib/apache-activemq/activemq-all-5.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 

Seems benign, but annoying. One possible fix for this is to remove slf4j jars from spring and amq. The Ducc's assembly script should exclude them from the DUCC tarball. The slf4j jars will be picked up from ducc_runtime/lib/slf4j dir.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira