[
https://issues.apache.org/jira/browse/LOG4J2-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720353#comment-15720353
]
Gary Gregory commented on LOG4J2-1723:
--------------------------------------
Thank you Ludovic!
All tests pass for me with {{mvn clean install}}:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 ..................................... SUCCESS [ 1.160 s]
[INFO] Apache Log4j API ................................... SUCCESS [ 17.925 s]
[INFO] Apache Log4j Core .................................. SUCCESS [16:56 min]
[INFO] Apache Log4j 1.x Compatibility API ................. SUCCESS [ 14.365 s]
[INFO] Apache Log4j SLF4J Binding ......................... SUCCESS [ 8.240 s]
[INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [ 3.892 s]
[INFO] Apache Log4j Commons Logging Bridge ................ SUCCESS [ 3.537 s]
[INFO] Apache Log4j Flume Bridge .......................... SUCCESS [ 22.287 s]
[INFO] Apache Log4j Web ................................... SUCCESS [ 7.206 s]
[INFO] Apache Log4j Tag Library ........................... SUCCESS [ 15.286 s]
[INFO] Apache Log4j JMX GUI ............................... SUCCESS [ 2.224 s]
[INFO] Apache Log4j Samples ............................... SUCCESS [ 0.180 s]
[INFO] Apache Log4j Samples: Flume - Common ............... SUCCESS [ 2.539 s]
[INFO] Apache Log4j Samples: Flume - Remote ............... SUCCESS [ 3.142 s]
[INFO] Apache Log4j Samples: Flume - Embedded ............. SUCCESS [ 4.704 s]
[INFO] Apache Log4j Samples: Configuration ................ SUCCESS [ 3.682 s]
[INFO] Apache Log4j Samples: LoggerProperties ............. SUCCESS [ 3.643 s]
[INFO] Apache Log4j Scala 2.11 wrapper for Log4j API ...... SUCCESS [ 24.312 s]
[INFO] Apache Log4j Samples: Scala API .................... SUCCESS [ 3.983 s]
[INFO] Apache Log4j OSGi .................................. SUCCESS [ 3.520 s]
[INFO] Apache Log4j BOM ................................... SUCCESS [ 0.582 s]
[INFO] Apache Log4j NoSQL ................................. SUCCESS [ 6.086 s]
[INFO] Apache Log4J Performance Tests ..................... SUCCESS [ 17.576 s]
[INFO] Apache Log4j Streaming Interface ................... SUCCESS [ 12.757 s]
[INFO] Apache Log4j JUL Adapter ........................... SUCCESS [ 10.721 s]
[INFO] Apache Log4j Liquibase Binding ..................... SUCCESS [ 3.230 s]
[INFO] Apache Log4j Scala 2.10 wrapper for Log4j API ...... SUCCESS [ 26.637 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20:42 min
[INFO] Finished at: 2016-12-04T10:15:57-08:00
[INFO] Final Memory: 50M/513M
[INFO] ------------------------------------------------------------------------
{noformat}
> Unwanted transitive dependency on geronimo-jms_1.1_spec
> -------------------------------------------------------
>
> 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
> Priority: Minor
> 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: [email protected]
For additional commands, e-mail: [email protected]
