You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ludovic HOCHET (JIRA)" <ji...@apache.org> on 2016/12/04 19:14:58 UTC

[jira] [Closed] (LOG4J2-1723) Unwanted transitive dependency on geronimo-jms_1.1_spec causes OSGi tests to fail

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

Ludovic HOCHET closed LOG4J2-1723.
----------------------------------

verified
mvn clean
mvn install
------------------------------------------------------------------------
Reactor Summary:

Apache Log4j 2 ..................................... SUCCESS [  1.102 s]
Apache Log4j API ................................... SUCCESS [ 19.421 s]
Apache Log4j Core .................................. SUCCESS [15:46 min]
Apache Log4j 1.x Compatibility API ................. SUCCESS [ 12.923 s]
Apache Log4j SLF4J Binding ......................... SUCCESS [  6.055 s]
Apache Log4j to SLF4J Adapter ...................... SUCCESS [  3.348 s]
Apache Log4j Commons Logging Bridge ................ SUCCESS [  3.111 s]
Apache Log4j Flume Bridge .......................... SUCCESS [ 29.384 s]
Apache Log4j Web ................................... SUCCESS [  6.400 s]
Apache Log4j Tag Library ........................... SUCCESS [ 15.212 s]
Apache Log4j JMX GUI ............................... SUCCESS [  2.317 s]
Apache Log4j Samples ............................... SUCCESS [  0.204 s]
Apache Log4j Samples: Flume - Common ............... SUCCESS [  2.760 s]
Apache Log4j Samples: Flume - Remote ............... SUCCESS [  2.799 s]
Apache Log4j Samples: Flume - Embedded ............. SUCCESS [  5.022 s]
Apache Log4j Samples: Configuration ................ SUCCESS [  2.827 s]
Apache Log4j Samples: LoggerProperties ............. SUCCESS [  3.070 s]
Apache Log4j Scala 2.11 wrapper for Log4j API ...... SUCCESS [ 21.843 s]
Apache Log4j Samples: Scala API .................... SUCCESS [  4.503 s]
Apache Log4j OSGi .................................. SUCCESS [  3.665 s]
Apache Log4j BOM ................................... SUCCESS [  1.616 s]
Apache Log4j NoSQL ................................. SUCCESS [  4.950 s]
Apache Log4J Performance Tests ..................... SUCCESS [ 15.634 s]
Apache Log4j Streaming Interface ................... SUCCESS [ 10.460 s]
Apache Log4j JUL Adapter ........................... SUCCESS [ 10.397 s]
Apache Log4j Liquibase Binding ..................... SUCCESS [  2.818 s]
Apache Log4j Scala 2.10 wrapper for Log4j API ...... SUCCESS [ 24.011 s]
------------------------------------------------------------------------
BUILD SUCCESS
------------------------------------------------------------------------
Total time: 19:24 min
Finished at: 2016-12-04T20:11:55+01:00
Final Memory: 51M/468M
------------------------------------------------------------------------


> Unwanted transitive dependency on geronimo-jms_1.1_spec causes OSGi tests to fail
> ---------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1723
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1723
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.7
>            Reporter: Ludovic HOCHET
>            Assignee: Gary Gregory
>            Priority: Minor
>             Fix For: 2.8
>
>         Attachments: patch-log4j2-1723.diff
>
>
> The change from maven-bundle-plugin:2.5.3 to 3.2.0, as part of the study of LOG4J2-1637, caused the dependency on package javax.jms to become non optional which made the OSGi tests to fails. Post LOG4J2-1637, LOG4J2-1664 was created to improve the OSGi tests and this problem was "offloaded" to it. Since this problem does not originate in the OSGi tests, I'm creating a new issue for it.
> Since this appeared with a change of maven-bundle-plugin, I had a look into how it processed optional dependencies since it was apparently not handling the optional declaration of jboss-jms-api_1.1_spec. As it happened it did add the javax.jms package from that dependency to the list of optional packages, but at the same time it was adding the same package to the list of required packages. Further checks showed that it was picking up the required package from geronimo-jms_1.1_spec which is a transitive dependency of activemq-broker (shown with dependency:tree). Since the JMS specifications are already included with jboss-jms-api_1.1_spec, the  geronimo-jms_1.1_spec should be excluded.



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

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