[jira] [Commented] (LOG4J2-1401) Support changing the log level for all messages related to some domain object

[ https://issues.apache.org/jira/browse/LOG4J2-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634971#comment-15634971 ] Remko Popma commented on LOG4J2-1401: - Quick overview of what the custom solution loo

[jira] [Commented] (LOG4J2-1637) OSGi support is broken in Log4j2 2.7

[ https://issues.apache.org/jira/browse/LOG4J2-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634770#comment-15634770 ] Ludovic HOCHET commented on LOG4J2-1637: Regarding the "javax.jms" issue: - it oc

[jira] [Commented] (LOG4J2-1637) OSGi support is broken in Log4j2 2.7

[ https://issues.apache.org/jira/browse/LOG4J2-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634666#comment-15634666 ] Remko Popma commented on LOG4J2-1637: - The LOG4J2-1660 changes are a good thing regar

[jira] [Deleted] (LOG4J2-1662) Allow for living in the JBoss application server world: java.nio.file.ProviderNotFoundException: Provider "vfs" not found

[ https://issues.apache.org/jira/browse/LOG4J2-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory deleted LOG4J2-1662: - > Allow for living in the JBoss application server world: > java.nio.file.ProviderNotFoundException

[jira] [Created] (LOG4J2-1662) Allow for living in the JBoss application server world: java.nio.file.ProviderNotFoundException: Provider "vfs" not found

Gary Gregory created LOG4J2-1662: Summary: Allow for living in the JBoss application server world: java.nio.file.ProviderNotFoundException: Provider "vfs" not found Key: LOG4J2-1662 URL: https://issues.apache.org/

Re: New version of Scala?

I don’t have a problem with it using the same groupId. Ralph > On Nov 3, 2016, at 1:06 PM, Matt Sicker wrote: > > Can we get a new git repo in the logging project for the Scala extensions > then? > > Also, if we use a different get repo, should we continue releasing these > log4j extras unde

Re: New version of Scala?

While maintaining a separate repo for log4j extras, should we try to keep the version numbers in sync? Could be less confusing (e.g., httpcomponents is somewhat confusing due to the version number mismatch between components), but there's also not much need to make new releases each time when the c

Re: svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml pom.xml src/changes/changes.xml

On Thu, Nov 3, 2016 at 3:35 PM, Remko Popma wrote: > Wrong list? > Indeed, sorry about that. Gary > > Sent from my iPhone > > On 4 Nov 2016, at 0:35, Gary Gregory wrote: > > Why not Java 7? > > Gary > > -- Forwarded message -- > From: > Date: Thu, Nov 3, 2016 at 4:44 AM > Su

Re: svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml pom.xml src/changes/changes.xml

Wrong list? Sent from my iPhone > On 4 Nov 2016, at 0:35, Gary Gregory wrote: > > Why not Java 7? > > Gary > > -- Forwarded message -- > From: > Date: Thu, Nov 3, 2016 at 4:44 AM > Subject: svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml > pom.xml src/chan

Re: New version of Scala?

Same group ID is yes for me. This is just a tool chain issue. Gary On Thu, Nov 3, 2016 at 1:06 PM, Matt Sicker wrote: > Can we get a new git repo in the logging project for the Scala extensions > then? > > Also, if we use a different get repo, should we continue releasing these > log4j extras u

[jira] [Closed] (LOG4J2-1658) 2.7 - ThreadContextAccess.getThreadContextMap NPE when specifying BasicContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker closed LOG4J2-1658. --- Fixed > 2.7 - ThreadContextAccess.getThreadContextMap NPE when specifying > BasicContextSelector >

[jira] [Commented] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634473#comment-15634473 ] Gary Gregory commented on LOG4J2-1587: -- FWIW: We've started using japicmp in Apache

Re: New version of Scala?

Can we get a new git repo in the logging project for the Scala extensions then? Also, if we use a different get repo, should we continue releasing these log4j extras under the same group ID? On 3 November 2016 at 14:57, Ralph Goers wrote: > Since we won’t be using Java 8 to perform releases any

[jira] [Comment Edited] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634060#comment-15634060 ] Ralph Goers edited comment on LOG4J2-1587 at 11/3/16 8:02 PM: -

[jira] [Commented] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634060#comment-15634060 ] Ralph Goers commented on LOG4J2-1587: - Even if you find an alternative to Clirr, I st

Re: New version of Scala?

Since we won’t be using Java 8 to perform releases any time soon I suggest the Scala support move to a different git repo with a separate build. Ralph > On Nov 3, 2016, at 8:20 AM, Matt Sicker wrote: > > This one will require Java 8 to compile. We'll need to update our build setup > to suppor

Re: New version of Scala?

I know Java 9 has a feature to let you include multiple versions of the same library for each JVM version. Not sure about the API enforcement, though. On 3 November 2016 at 11:02, Gary Gregory wrote: > You just have to build with Java 8... we could use the animal sniffer > plugin to sandbox the

[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.7 > Support Scala 2.12.0 > > > Key:

[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: API > Support Scala 2.12.0 > > > Key: LOG4J

[jira] [Assigned] (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 reassigned LOG4J2-1661: -- Assignee: Mikael Ståldal > Support Scala 2.12.0 > > >

[jira] [Closed] (LOG4J2-1657) File logger prevents Gelf appender/logger to logging to server, if removed.

[ https://issues.apache.org/jira/browse/LOG4J2-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1657. -- > File logger prevents Gelf appender/logger to logging to server, if removed. > ---

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

Gary Gregory created LOG4J2-1661: Summary: Support Scala 2.12.0 Key: LOG4J2-1661 URL: https://issues.apache.org/jira/browse/LOG4J2-1661 Project: Log4j 2 Issue Type: Improvement Re

Re: New version of Scala?

Tracking here https://issues.apache.org/jira/browse/LOG4J2-1661 Gary On Thu, Nov 3, 2016 at 9:02 AM, Gary Gregory wrote: > You just have to build with Java 8... we could use the animal sniffer > plugin to sandbox the other modules to Java 7. > > We could requires Java 8 for all of Log4j ... hid

Re: New version of Scala?

You just have to build with Java 8... we could use the animal sniffer plugin to sandbox the other modules to Java 7. We could requires Java 8 for all of Log4j ... hides from flying tomatoes ;-) Does Java 9 talk about adding some new compiler flag to kind of do what the animal sniffer plugin does?

Re: New version of Scala?

I am not sure how to best configure Maven either. However, I think that a good start would be to make it possible to build everything with Java 8: https://issues.apache.org/jira/browse/LOG4J2-1587 On Thu, Nov 3, 2016 at 4:55 PM, Matt Sicker wrote: > So yes, it does sound like we'd need a 2.12

[jira] [Updated] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1587: --- Affects Version/s: 2.7 > Build process should work on Java 8 > --

[jira] [Commented] (LOG4J2-1637) OSGi support is broken in Log4j2 2.7

[ https://issues.apache.org/jira/browse/LOG4J2-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633236#comment-15633236 ] Gary Gregory commented on LOG4J2-1637: -- FWIW, this is the SAME errors I saw before R

Re: New version of Scala?

So yes, it does sound like we'd need a 2.12 module now as well. I'm not exactly sure how to best configure maven to do a build like this. On 3 November 2016 at 10:31, Mikael Ståldal wrote: > Since different Scala versions are not binary compatible, we need a new > module to support Scala 2.12 (t

[jira] [Commented] (LOG4J2-1637) OSGi support is broken in Log4j2 2.7

[ https://issues.apache.org/jira/browse/LOG4J2-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633212#comment-15633212 ] Gary Gregory commented on LOG4J2-1637: -- With the latest: {noformat}

Fwd: svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml pom.xml src/changes/changes.xml

Why not Java 7? Gary -- Forwarded message -- From: Date: Thu, Nov 3, 2016 at 4:44 AM Subject: svn commit: r1767873 - in /commons/proper/daemon/trunk: build.xml pom.xml src/changes/changes.xml To: [email protected] Author: markt Date: Thu Nov 3 11:44:02 2016 New Revisi

Re: New version of Scala?

Since different Scala versions are not binary compatible, we need a new module to support Scala 2.12 (that's why we have two modules already, for Scala 2.10 and 2.11). And that new module will require Java 8. On Thu, Nov 3, 2016 at 4:25 PM, Gary Gregory wrote: > Oops I skipped typing the 8! > >

Re: New version of Scala?

It's okay; we read your mind. :-) Sent from my iPhone > On 4 Nov 2016, at 0:25, Gary Gregory wrote: > > Oops I skipped typing the 8! > > >> On Nov 3, 2016 8:20 AM, "Matt Sicker" wrote: >> This one will require Java 8 to compile. We'll need to update our build >> setup to support it. >> >>>

Re: New version of Scala?

Oops I skipped typing the 8! On Nov 3, 2016 8:20 AM, "Matt Sicker" wrote: > This one will require Java 8 to compile. We'll need to update our build > setup to support it. > > On 3 November 2016 at 10:14, Gary Gregory wrote: > >> Do we need a new module to support Scala 2.12? >> http://www.scala

Re: New version of Scala?

Mixing java versions in the build sounds painful... Shall we ask Mikael if he really wants this? On Fri, Nov 4, 2016 at 12:20 AM, Matt Sicker wrote: > This one will require Java 8 to compile. We'll need to update our build > setup to support it. > > On 3 November 2016 at 10:14, Gary Gregory wro

Re: New version of Scala?

This one will require Java 8 to compile. We'll need to update our build setup to support it. On 3 November 2016 at 10:14, Gary Gregory wrote: > Do we need a new module to support Scala 2.12? http://www.scala-lang.org/ > news/2.12.0? It does require Java I think. > > Gary > -- Matt Sicker

[jira] [Commented] (LOG4J2-1648) Provide ability for users to put non-String values in the ThreadContext

[ https://issues.apache.org/jira/browse/LOG4J2-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633073#comment-15633073 ] Remko Popma commented on LOG4J2-1648: - I will check that SortedArrayStringMap correct

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

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Issue Comment Deleted] (LOG4J2-1648) Provide ability for users to put non-String values in the ThreadContext

[ https://issues.apache.org/jira/browse/LOG4J2-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1648: Comment: was deleted (was: I will check that SortedArrayStringMap correctly handles values that are

[jira] [Commented] (LOG4J2-1648) Provide ability for users to put non-String values in the ThreadContext

[ https://issues.apache.org/jira/browse/LOG4J2-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633064#comment-15633064 ] Remko Popma commented on LOG4J2-1648: - I will check that SortedArrayStringMap correct

New version of Scala?

Do we need a new module to support Scala 2.12? http://www.scala-lang.org/news/2.12.0? It does require Java I think. Gary

[jira] [Commented] (LOG4J2-1637) OSGi support is broken in Log4j2 2.7

[ https://issues.apache.org/jira/browse/LOG4J2-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633029#comment-15633029 ] Remko Popma commented on LOG4J2-1637: - The changes for LOG4J2-1660 are pushed to mast

[jira] [Closed] (LOG4J2-1660) ThreadContext to expose ReadOnlyThreadContextMap internal data structure

[ https://issues.apache.org/jira/browse/LOG4J2-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1660. --- Resolution: Fixed Fixed in master. Added public method {{ThreadContext::getThreadContextMap}}, remov

[jira] [Updated] (LOG4J2-1660) ThreadContext to expose ReadOnlyThreadContextMap internal data structure

[ https://issues.apache.org/jira/browse/LOG4J2-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1660: Description: Add public method {{ThreadContext::getThreadContextMap}} that returns a {{ReadOnlyThr

[jira] [Updated] (LOG4J2-1629) Support for primitive values in StringMap

[ https://issues.apache.org/jira/browse/LOG4J2-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1629: Description: For some applications like financial trading systems, highly interactive games or num

[jira] [Closed] (LOG4J2-1401) Support changing the log level for all messages related to some domain object

[ https://issues.apache.org/jira/browse/LOG4J2-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1401. --- Resolution: Won't Fix Based on the work done for LOG4J2-1010 (Injectable context properties), LOG4J2

[jira] [Closed] (LOG4J2-1607) Improve performance of SortedArrayStringMap data structure

[ https://issues.apache.org/jira/browse/LOG4J2-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1607. --- Resolution: Won't Fix After some experimentation I found that the idea I had did not work very well.

Re: Version number of next release

Okay, I removed version 2.7.1 from Jira and moved the Jira tickets that were fixed for 2.7.1 to 2.8. On Thu, Nov 3, 2016 at 6:09 PM, Mikael Ståldal wrote: > Yes, seems reasonable. > > On Thu, Nov 3, 2016 at 9:29 AM, Gary Gregory > wrote: > >> On Thu, Nov 3, 2016 at 1:08 AM, Remko Popma >> wrot

Re: Version number of next release

Yes, seems reasonable. On Thu, Nov 3, 2016 at 9:29 AM, Gary Gregory wrote: > On Thu, Nov 3, 2016 at 1:08 AM, Remko Popma wrote: > >> Considering that LOG4J2-1660 >> is an API change, >> the next release should probably have version number 2.8

[jira] [Updated] (LOG4J2-1659) Facilitate shading Log4j into an application's uber jar

[ https://issues.apache.org/jira/browse/LOG4J2-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1659: - Attachment: logging-log4j2.patch > Facilitate shading Log4j into an application's uber jar >

[jira] [Updated] (LOG4J2-1659) Facilitate shading Log4j into an application's uber jar

[ https://issues.apache.org/jira/browse/LOG4J2-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1659: - Attachment: (was: logging-log4j2.patch) > Facilitate shading Log4j into an application's uber

[jira] [Updated] (LOG4J2-1659) Facilitate shading Log4j into an application's uber jar

[ https://issues.apache.org/jira/browse/LOG4J2-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1659: - Attachment: logging-log4j2.patch I have attached my proposal. The build passes locally for me. H

Jenkins build became unstable: Log4j 2.x #2425

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: Version number of next release

On Thu, Nov 3, 2016 at 1:08 AM, Remko Popma wrote: > Considering that LOG4J2-1660 > is an API change, the > next release should probably have version number 2.8 instead of 2.7.1. > Thoughts? > SemVer would say "yes". Fine with me. Gary -- E

[jira] [Resolved] (LOG4J2-1658) 2.7 - ThreadContextAccess.getThreadContextMap NPE when specifying BasicContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1658. - Resolution: Fixed Fixed in master. Please verify and close. > 2.7 - ThreadContextAccess.getThrea

[jira] [Updated] (LOG4J2-1658) 2.7 - ThreadContextAccess.getThreadContextMap NPE when specifying BasicContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1658: Fix Version/s: 2.8 > 2.7 - ThreadContextAccess.getThreadContextMap NPE when specifying > BasicCont

Version number of next release

Considering that LOG4J2-1660 is an API change, the next release should probably have version number 2.8 instead of 2.7.1. Thoughts?

[jira] [Commented] (LOG4J2-1658) 2.7 - ThreadContextAccess.getThreadContextMap NPE when specifying BasicContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631997#comment-15631997 ] Remko Popma commented on LOG4J2-1658: - Looking at this again, I am not sure that modi

[jira] [Commented] (LOG4J2-1658) 2.7 - ThreadContextAccess.getThreadContextMap NPE when specifying BasicContextSelector

[ https://issues.apache.org/jira/browse/LOG4J2-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631961#comment-15631961 ] Remko Popma commented on LOG4J2-1658: - Thanks, that is helpful! > 2.7 - ThreadContex