Re: [Log4j] release 2.9 - Scala API

The code as is should be ready for source and binary artifacts I believe. I don't recall if there was a distribution zip task already set up, though, and I believe that's the minimal required artifacts for an Apache release. On 6 July 2017 at 17:19, Gary Gregory wrote: >

Re: [Log4j] release 2.9 - Scala API

On Thu, Jul 6, 2017 at 2:31 PM, Matt Sicker wrote: > I attempted a release, and we fixed something, but I was still unsure as to > how to build the website as the site:stage goal fails with missing file > errors if I recall correctly. Since then, I've been busy with a short

Re: [Log4j] release 2.9 - Scala API

I attempted a release, and we fixed something, but I was still unsure as to how to build the website as the site:stage goal fails with missing file errors if I recall correctly. Since then, I've been busy with a short term work project eating up all my energy, so I haven't had a chance to make

Re: [Log4j] release 2.9 - Scala API

Don’t we still need to get Scala integrated into the web site? Can we do that before the 2.9 release? Or has a Scala release not been done yet? Ralph > On Jul 6, 2017, at 1:15 PM, Mikael Ståldal wrote: > > Yes, I think that the 11.0 release of the Scala API should only be

[jira] [Updated] (LOG4J2-1690) Scala wrapper for Context map

[ https://issues.apache.org/jira/browse/LOG4J2-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1690: --- Affects Version/s: 2.8 2.8.1 2.8.2 > Scala

[jira] [Updated] (LOG4J2-1661) Support Scala 2.12.0

[ https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1661: --- Affects Version/s: 2.8 2.8.1 2.8.2 > Support

[jira] [Updated] (LOG4J2-1661) Support Scala 2.12.0

[ https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1661: --- Component/s: (was: API) Scala API > Support Scala 2.12.0 >

[jira] [Resolved] (LOG4J2-1942) Scala library for scala 2.12 not released to maven central

[ https://issues.apache.org/jira/browse/LOG4J2-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1942. Resolution: Duplicate > Scala library for scala 2.12 not released to maven central >

Re: [Log4j] release 2.9 - Scala API

Yes, I think that the 11.0 release of the Scala API should only be what we currently have in 2.8.2 plus Scala 2.12 support plus the already implemented ThreadContext wrapper in LOG4J2-1690. Basically just release what we currently have in the logging-log4j-scala Git repo. On 2017-07-05

Jenkins build is unstable: Log4j 2.x #2873

See

[jira] [Commented] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

[ https://issues.apache.org/jira/browse/LOGCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076641#comment-16076641 ] Simon Heath commented on LOGCXX-489: That would do it. The version there builds fine. Thank you!

[jira] [Commented] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

[ https://issues.apache.org/jira/browse/LOGCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076535#comment-16076535 ] Simon Heath commented on LOGCXX-489: Sorry for the duplicate in that case! I tried to search existing

Re: Classes found in the wrong directory: {META-INF/versions/9/org/apache/logging/log4j/util/StackLocator.class=org.apache.logging.log4j.util.StackLocator}

If you don't run clean then the OSGi plugin will barf over those classes as it does not ignore classes in the "wrong" place, it doesn't support java 9, and it doesn't support multi-release jars. I have opened an issue on the Felix maven bundle plugin that is being ignored. Short answer. You

Build failed in Jenkins: Log4j 2.x #2872

See Changes: [ggregory] Add missing '@Override' annotations. [ggregory] Add missing '@Deprecated' annotations. [ggregory] Remove unused imports. -- [...truncated 551.16

[jira] [Updated] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YU Chang updated LOG4J2-1969: - Description: I have a spring boot(v1.5.4) web application which use log4j-2.7 for logging. It works well

[jira] [Updated] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YU Chang updated LOG4J2-1969: - Description: I have a spring boot(v1.5.4) web application which use log4j-2.7 for logging. It works well

[jira] [Updated] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YU Chang updated LOG4J2-1969: - Description: I have a spring boot(v1.5.4) web application which use log4j-2.7 for logging. It works well

[jira] [Updated] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YU Chang updated LOG4J2-1969: - Description: I have a spring boot(v1.5.4) web application which use log4j-2.7 for logging. It works well

[jira] [Updated] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YU Chang updated LOG4J2-1969: - Description: I have a spring boot(v1.5.4) web application which use log4j-2.7 for logging. It works well

[jira] [Updated] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

[ https://issues.apache.org/jira/browse/LOG4J2-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YU Chang updated LOG4J2-1969: - Description: I have a spring boot(v1.5.4) web application which use log4j-2.7 for logging. It works well

[jira] [Created] (LOG4J2-1969) TcpSocketServer does not replace any “{}” in message

YU Chang created LOG4J2-1969: Summary: TcpSocketServer does not replace any “{}” in message Key: LOG4J2-1969 URL: https://issues.apache.org/jira/browse/LOG4J2-1969 Project: Log4j 2 Issue Type:

[jira] [Resolved] (LOG4J2-1961) Reconfigure breaks DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1961. -- Resolution: Fixed Fix Version/s: 2.9 In Git master now. Please verify and close. >

[jira] [Commented] (LOG4J2-1961) Reconfigure breaks DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076286#comment-16076286 ] ASF subversion and git services commented on LOG4J2-1961: - Commit

[jira] [Updated] (LOG4J2-1931) Wrong Date is calculated for rollover filePattern with timezone parameter

[ https://issues.apache.org/jira/browse/LOG4J2-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1931: - Description: Wrong Date is calculated for rollover filePattern with timezone parameter. Due to

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076271#comment-16076271 ] Gary Gregory commented on LOG4J2-1768: -- Ping? > MDC.clear() is broken in Log4j-1_2-api = 2.4 >

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076259#comment-16076259 ] Ajitha commented on LOG4J2-1921: Android does not support Java 9 classes. It says: {code:java} AGPBI:

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076240#comment-16076240 ] Ajitha commented on LOG4J2-1921: My bad! Firewall block. It identified the build now. Will update you

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076232#comment-16076232 ] Ajitha commented on LOG4J2-1921: {code:java} Error:(11, 0) Could not find method snapshot() for

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076230#comment-16076230 ] Gary Gregory edited comment on LOG4J2-1921 at 7/6/17 9:23 AM: -- How about:

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076217#comment-16076217 ] Ajitha commented on LOG4J2-1921: No luck it says: Error:Failed to resolve:

[jira] [Resolved] (LOG4J2-1912) CompositeConfiguration logs warning "Unable to determine URI for configuration." However, the reconfiguration is completed.

[ https://issues.apache.org/jira/browse/LOG4J2-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1912. -- Resolution: Fixed Hi [~rri], Thank you for your report. A fix is in Git master. Please

[jira] [Commented] (LOG4J2-1912) CompositeConfiguration logs warning "Unable to determine URI for configuration." However, the reconfiguration is completed.

[ https://issues.apache.org/jira/browse/LOG4J2-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076194#comment-16076194 ] ASF subversion and git services commented on LOG4J2-1912: - Commit

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076193#comment-16076193 ] Ajitha commented on LOG4J2-1921: ok, in my Android gradle build, I added maven { url

[jira] [Updated] (LOG4J2-1912) CompositeConfiguration logs warning "Unable to determine URI for configuration." However, the reconfiguration is completed.

[ https://issues.apache.org/jira/browse/LOG4J2-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1912: - Summary: CompositeConfiguration logs warning "Unable to determine URI for configuration."

[log4net] test failure

Hi, looks like thepipeline found a test failure and at first sight this should not be possible with exclusive locks. So this is a hint towards a race condition that exists in the rolling file appender. This failure could be the root cause of several issues and unexpected behavior. I thought to

Jenkins build is back to stable : Log4j 2.x #2868

See

Fwd: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #72

This just happened now for the first time. Hasn't happened before and might be gone with a rebuild. Still, has anyone seen this (or something similar) before? [csc] Compiling 226 files to

[jira] [Commented] (LOG4J2-1967) Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076159#comment-16076159 ] Gary Gregory commented on LOG4J2-1967: -- Hi [~paulk95], I added two tests that pass in 2.9-SNAPSHOT:

[jira] [Commented] (LOG4J2-1967) Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076153#comment-16076153 ] ASF subversion and git services commented on LOG4J2-1967: - Commit

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076142#comment-16076142 ] Gary Gregory edited comment on LOG4J2-1921 at 7/6/17 8:15 AM: -- That site

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076142#comment-16076142 ] Gary Gregory commented on LOG4J2-1921: -- That site does not pick up SNAPSHOT builds. You need to

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076138#comment-16076138 ] Ajitha commented on LOG4J2-1921: Thanks. But when can I expect it to get updated in

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076125#comment-16076125 ] Gary Gregory commented on LOG4J2-1921: -- Note that the current SNAPSHOT version was updated to

[jira] [Closed] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1964. Closing per [~phymbert]. > Dynamic reconfiguration does not work for filePattern of RollingFile >

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076119#comment-16076119 ] Ajitha edited comment on LOG4J2-1921 at 7/6/17 7:54 AM: Yes it is exactly 460

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076119#comment-16076119 ] Ajitha edited comment on LOG4J2-1921 at 7/6/17 7:52 AM: Yes it is exactly 460

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076119#comment-16076119 ] Ajitha commented on LOG4J2-1921: Yes it is exactly https://issues.apache.org/jira/browse/LOG4J2-460. I

[jira] [Updated] (LOG4J2-1967) Unable to invoke factory method in class class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1967: - Description: We have been using log4j2 version 2.7 for a while and recently we have upgraded to

[jira] [Commented] (LOG4J2-1725) RollingFileAppender's filePattern not reloaded when using monitorInterval

[ https://issues.apache.org/jira/browse/LOG4J2-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076109#comment-16076109 ] Pierrick HYMBERT commented on LOG4J2-1725: -- Resolved and in git master, thank you. >

[jira] [Commented] (LOG4J2-1964) Dynamic reconfiguration does not work for filePattern of RollingFile

[ https://issues.apache.org/jira/browse/LOG4J2-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076108#comment-16076108 ] Pierrick HYMBERT commented on LOG4J2-1964: -- Hi [~garydgregory] , looks good thank you >

Classes found in the wrong directory: {META-INF/versions/9/org/apache/logging/log4j/util/StackLocator.class=org.apache.logging.log4j.util.StackLocator}

Hi All, When I run certain mvn commands, I get: [INFO] --- maven-bundle-plugin:3.3.0:manifest (default) @ log4j-api --- [ERROR] Manifest org.apache.logging.log4j:log4j-api:jar:2.9-SNAPSHOT : Classes found in the wrong directory: {META-INF/versions/9/org/apache/logging/log4j/util/

[jira] [Resolved] (LOGCXX-489) log4cxx-0.10.0 - socketoutputstream.cpp:52: error: 'memcpy' was not declared in this scope

[ https://issues.apache.org/jira/browse/LOGCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-489. -- Resolution: Fixed Fix Version/s: 0.11.0 This sounds exactly like already