[jira] [Commented] (LOG4J2-1192) Dynamic Subject for SMTP Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537916#comment-15537916 ] Gary Gregory commented on LOG4J2-1192: -- Hello Harry, Are you available to provide a patch?

[jira] [Commented] (LOG4J2-1192) Dynamic Subject for SMTP Appender

[ https://issues.apache.org/jira/browse/LOG4J2-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537905#comment-15537905 ] Harry Bawls commented on LOG4J2-1192: - The implementation of this feature does not work. (or at least

Re: Modules

> On 1 Oct 2016, at 13:05, Ralph Goers wrote: > > I don’t cut a release branch. The Maven release plugin updates the pom > versions, creates the release tag, and then changes the pom version to be a > snapshot. It then essentially does a mvn deploy on the tag. The

Re: Modules

I don’t cut a release branch. The Maven release plugin updates the pom versions, creates the release tag, and then changes the pom version to be a snapshot. It then essentially does a mvn deploy on the tag. The release plugin typically performs a build against the snapshot to confirm the build

Re: Modules

On Fri, Sep 30, 2016 at 8:03 PM, Remko Popma wrote: > Thanks! > Were you thinking of doing a release as an "exercise" to improve the process? ;-) Gary > > Sent from my iPhone > > On 1 Oct 2016, at 11:34, Gary Gregory wrote: > > On Sep 30, 2016

Re: Modules

Thanks! Sent from my iPhone > On 1 Oct 2016, at 11:34, Gary Gregory wrote: > > On Sep 30, 2016 7:15 PM, "Remko Popma" wrote: > > > > Can anyone send a link to the release procedures? > > http://wiki.apache.org/logging/Log4j2ReleaseGuide > >

Re: Modules

On Sep 30, 2016 7:15 PM, "Remko Popma" wrote: > > Can anyone send a link to the release procedures? http://wiki.apache.org/logging/Log4j2ReleaseGuide Gary > > Sent from my iPhone > > On 1 Oct 2016, at 2:31, Ralph Goers wrote: > >> I would have

Re: Modules

Can anyone send a link to the release procedures? Sent from my iPhone > On 1 Oct 2016, at 2:31, Ralph Goers wrote: > > I would have a “core” project and an “extras”, “extensions” or some other > name. They are all already separate jars. I just want to split them

Re: Modules

Sent from my iPhone > On 1 Oct 2016, at 2:04, Ralph Goers wrote: > > Actually, I just created LOG4J2-1627 for this and I specifically did bring > Java 9 modules into the discussion because they should at least be considered > along with the Java 8 profiles. Right

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537567#comment-15537567 ] Matt Sicker commented on LOG4J2-1628: - Public repo for all apache project snapshots is here:

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537487#comment-15537487 ] Remko Popma commented on LOG4J2-1628: - You can build with {{mvn -DskipTests clean install}}. That is

[jira] [Comment Edited] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537413#comment-15537413 ] Remko Popma edited comment on LOG4J2-1628 at 10/1/16 12:08 AM: --- Mark, the

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537468#comment-15537468 ] Mark Bowman commented on LOG4J2-1628: - The core module of log4j2 master doesn't build for me. Failed

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537432#comment-15537432 ] Mark Bowman commented on LOG4J2-1628: - Is their a public repo for nightly-build maven artifacts or do

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537413#comment-15537413 ] Remko Popma commented on LOG4J2-1628: - Mark, the problem description of scrambled messages reminded

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537384#comment-15537384 ] Mark Bowman commented on LOG4J2-1628: - Yes, the link is intranet. I'll try and get an answer on why

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537373#comment-15537373 ] Gary Gregory commented on LOG4J2-1628: -- As an aside, could you describe in a separate ticket how

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537325#comment-15537325 ] Mark Bowman commented on LOG4J2-1628: - {noformat} package org.lcogt.commons.log; import

[jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15537317#comment-15537317 ] Gary Gregory commented on LOG4J2-1628: -- Can do describe or post {{LCOGTLayout}} SVP? > File locking

[jira] [Created] (LOG4J2-1628) File locking regression for Async FileAppender

Mark Bowman created LOG4J2-1628: --- Summary: File locking regression for Async FileAppender Key: LOG4J2-1628 URL: https://issues.apache.org/jira/browse/LOG4J2-1628 Project: Log4j 2 Issue Type:

Re: [VOTE] Release Log4j 2.7-rc1

On Thu, Sep 29, 2016 at 10:05 AM, Gary Gregory wrote: > Please wait to cut rc2, I am fixing a regression: > https://issues.apache.org/jira/browse/LOG4J2-1620 > Fixed. This looks like it needs addressing: https://issues.apache.org/jira/browse/LOG4J2-1618 Gary > > Gary

[jira] [Comment Edited] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536624#comment-15536624 ] Gary Gregory edited comment on LOG4J2-1588 at 9/30/16 6:19 PM: --- +1, this is

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536624#comment-15536624 ] Gary Gregory commented on LOG4J2-1588: -- +1, this is a _perfect_ use case for the

Re: Modules

I would have a “core” project and an “extras”, “extensions” or some other name. They are all already separate jars. I just want to split them out because they don’t (or shouldn’t) change nearly as often as the core stuff - although we may get to the point where core is pretty stable and we are

Re: Modules

I think your opinion would change if you tried to do the release. Ralph > On Sep 30, 2016, at 10:05 AM, Gary Gregory wrote: > > Right, hence this thread ;-) I am not hot about having multiple builds FYIW. > > Gary > > On Fri, Sep 30, 2016 at 9:59 AM, Matt Sicker

Re: Modules

Oh, and FWIW, I have never really been interested in the uber jar. To me, the bom is really all that is required for that. Ralph > On Sep 30, 2016, at 10:04 AM, Ralph Goers wrote: > > Actually, I just created LOG4J2-1627 for this and I specifically did bring >

Re: Modules

Increased modularity is the OSGi way, but it's also a hard thing to convince people of. I've met many developers (notably Spring fanboys) that are still in a monolithic classpath mindset of "why bother splitting this up?" Anyways, Ralph, are you proposing spinning out the non-core stuff into a

Re: Modules

Right, hence this thread ;-) I am not hot about having multiple builds FYIW. Gary On Fri, Sep 30, 2016 at 9:59 AM, Matt Sicker wrote: > Oh wait, Ralph is talking about something else entirely. > > On 30 September 2016 at 11:58, Matt Sicker wrote: > >> I

Re: Modules

Actually, I just created LOG4J2-1627 for this and I specifically did bring Java 9 modules into the discussion because they should at least be considered along with the Java 8 profiles. Right now I am sure we have stuff that would create problems with trying to run in compact profiles 1 and 2.

Re: Modules

Oh wait, Ralph is talking about something else entirely. On 30 September 2016 at 11:58, Matt Sicker wrote: > I think log4j-nosql could be merged into log4j-core. > > On 30 September 2016 at 11:50, Gary Gregory > wrote: > >> Ralph recently mentions that

Re: Modules

I think log4j-nosql could be merged into log4j-core. On 30 September 2016 at 11:50, Gary Gregory wrote: > Ralph recently mentions that he'd like some modules removed while Matt > mentioned merging some back into Core. > > Shall we discuss this on the ML instead of Jira?

[jira] [Updated] (LOG4J2-1627) Move components from the Log4j 2 build into a separate build.

[ https://issues.apache.org/jira/browse/LOG4J2-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-1627: Description: The Log4j build has grown to the point that performing releases is very time

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536451#comment-15536451 ] Ralph Goers commented on LOG4J2-1626: - I created LOG4J2-1627. Moving things back into core is

[jira] [Created] (LOG4J2-1627) Move components from the Log4j 2 build into a separate build.

Ralph Goers created LOG4J2-1627: --- Summary: Move components from the Log4j 2 build into a separate build. Key: LOG4J2-1627 URL: https://issues.apache.org/jira/browse/LOG4J2-1627 Project: Log4j 2

Modules

Ralph recently mentions that he'd like some modules removed while Matt mentioned merging some back into Core. Shall we discuss this on the ML instead of Jira? I could also see doing an uber jar (mod the mutually exclusive jars) and reorging the system with a smaller core (everything except

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536417#comment-15536417 ] Matt Sicker commented on LOG4J2-1626: - Could you make a new issue to discuss which modules you'd like

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15536094#comment-15536094 ] Ralph Goers commented on LOG4J2-1588: - My 2 cents. I agree with Mikael. This is exactly what the

[jira] [Comment Edited] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535923#comment-15535923 ] Remko Popma edited comment on LOG4J2-1588 at 9/30/16 12:57 PM: --- You should

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535923#comment-15535923 ] Remko Popma commented on LOG4J2-1588: - You should be able to control the behavior with [this system

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535875#comment-15535875 ] Mikael Ståldal commented on LOG4J2-1588: Maybe you can use Thread Content Map (also known as MDC)

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535789#comment-15535789 ] Rainer Schnitker commented on LOG4J2-1588: -- The log4j version 2.5 is also ok. Only affects

[jira] [Comment Edited] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535783#comment-15535783 ] Rainer Schnitker edited comment on LOG4J2-1588 at 9/30/16 11:51 AM:

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535783#comment-15535783 ] Rainer Schnitker commented on LOG4J2-1588: -- This issure affects version 2.6.2. Perhaps there are

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535753#comment-15535753 ] Ralph Goers commented on LOG4J2-1626: - All releases are done on OS/X. I will restate. I will veto

[jira] [Commented] (LOG4J2-1501) FileAppender should be able to create files on-demand

[ https://issues.apache.org/jira/browse/LOG4J2-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535452#comment-15535452 ] Remko Popma commented on LOG4J2-1501: - [~garydgregory] in the [Appenders

[jira] [Commented] (LOG4J2-1504) RollingFileAppender should be able to create files on-demand

[ https://issues.apache.org/jira/browse/LOG4J2-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535454#comment-15535454 ] Remko Popma commented on LOG4J2-1504: - [~garydgregory] in the [Appenders

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535382#comment-15535382 ] Mikael Ståldal commented on LOG4J2-1626: I don't use Windows either. > Port Windows Event Log

Re: [jira] [Comment Edited] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

It's possible to write to the event log using .NET; e.g. https://support.microsoft.com/en-us/kb/301279 ... It's also possible to compile .NET on Linux ... https://www.microsoft.com/net/core#ubuntu So lack of Windows may (*) not be that much of a show-stopper. (*) I say may, because I wonder if

[jira] [Commented] (LOG4J2-1626) Port Windows Event Log Appender from Log4j 1.2

[ https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15535243#comment-15535243 ] Gary Gregory commented on LOG4J2-1626: -- Maybe... > Port Windows Event Log Appender from Log4j 1.2 >