[GitHub] [logging-log4j-kotlin] roedll edited a comment on pull request #13: Ensure OSGi compatibility

2020-11-10 Thread GitBox
roedll edited a comment on pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13#issuecomment-725226670 The standard path for bnd metadata seems to be the "\/bnd.bnd" (like defined here https://bnd.bndtools.org/md/805-instructions.html in section "Headers")

[GitHub] [logging-log4j-kotlin] roedll commented on pull request #13: Ensure OSGi compatibility

2020-11-10 Thread GitBox
roedll commented on pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13#issuecomment-725226670 The standard path for bnd metadata seems to be the "/bnd.bnd" (like defined here https://bnd.bndtools.org/md/805-instructions.html in section "Headers") I've now

[jira] [Commented] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

2020-11-10 Thread Matt Sicker (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229534#comment-17229534 ] Matt Sicker commented on LOG4J2-2025: - I believe it's because it was a new feature,

[jira] [Commented] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

2020-11-10 Thread Ilamparithi Natarajan (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229532#comment-17229532 ] Ilamparithi Natarajan commented on LOG4J2-2025: --- [~rgoers] I plan to to us

[GitHub] [logging-log4j-kotlin] roedll commented on pull request #13: Ensure OSGi compatibility

2020-11-10 Thread GitBox
roedll commented on pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13#issuecomment-724917908 No problem - Done This is an automated message from the Apache Git Service. To respond to the message,

[GitHub] [logging-log4j-kotlin] rocketraman commented on pull request #13: Ensure OSGi compatibility

2020-11-10 Thread GitBox
rocketraman commented on pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13#issuecomment-724861595 Thanks for this. I'd like to see the `bnd` definition file in a subdirectory rather than at the root e.g. `bnd/log4j-kotlin-api.bnd` ``` b

[CI][UNSTABLE] Logging/log4j/master#177 has test failures

2020-11-10 Thread Mr. Jenkins
BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/master/177/ Project: master Date of build: Tue, 10 Nov 2020 15:43:00 + Build duration: 1 hr 54 min and counting JUnit Tests Name: liquibase.ext.logging.log4j2 Failed:

[GitHub] [logging-log4j-kotlin] roedll opened a new pull request #13: Ensure OSGi compatibility

2020-11-10 Thread GitBox
roedll opened a new pull request #13: URL: https://github.com/apache/logging-log4j-kotlin/pull/13 We are using the Log4J Kotlin API in an OSGi environment. One pitfall is the missing manifest headers that would enable the direct usage as OSGi bundle. We are currently working with a workara

[jira] [Commented] (LOG4J2-2927) ErrorHandlers on Appenders cannot be configured.

2020-11-10 Thread Yuanzhe Geng (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229296#comment-17229296 ] Yuanzhe Geng commented on LOG4J2-2927: --- Sorry. I have been busy recently,and I wi

[jira] [Commented] (LOG4J2-2927) ErrorHandlers on Appenders cannot be configured.

2020-11-10 Thread Jenn (Jira)
[ https://issues.apache.org/jira/browse/LOG4J2-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229293#comment-17229293 ] Jenn commented on LOG4J2-2927: -- Just out of curiosity, has there been any progress on this

[GitHub] [logging-log4j2] vy commented on pull request #436: LOG4J2-2850 Fix ctor used in LocalizedMessageFactory#newMessage().

2020-11-10 Thread GitBox
vy commented on pull request #436: URL: https://github.com/apache/logging-log4j2/pull/436#issuecomment-724676679 Thanks so much @sandeepbarnwal! Would you mind updating `/src/changes/changes.xml` and adding a simple test (to `LocalizedMessageTest`?) as well, please? -