Re: 2.6 is not source compatible with 2.5

Great, TY. Gary On May 29, 2016 8:20 PM, "Ralph Goers" wrote: > I added the same information to the main site page. > > Ralph > > On May 29, 2016, at 2:08 PM, Gary Gregory wrote: > > On Sun, May 29, 2016 at 1:41 PM, Ralph Goers

Re: 2.6 is not source compatible with 2.5

I added the same information to the main site page. Ralph > On May 29, 2016, at 2:08 PM, Gary Gregory wrote: > > On Sun, May 29, 2016 at 1:41 PM, Ralph Goers > wrote: > Here is the text that I propose to

Re: org.apache.logging.log4j.util.Unbox.isBoxedPrimitive(StringBuilder)

It prevents primitives from being auto-boxed in a Number object. Common usage would be static import of the methods in this class, so the class name is not visible in the code. The code then looks like logger.debug("...{}", box(3.14)); Which communicates to the reader that we are manually

[ANNOUNCEMENT] Log4j 2.6 released

Apache Log4j 2.6 RELEASE NOTES The Apache Log4j 2 team is pleased to announce the Log4j 2.6 release! Apache log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x,

Re: 2.6 is not source compatible with 2.5

On Sun, May 29, 2016 at 1:41 PM, Ralph Goers wrote: > Here is the text that I propose to add to the announcement. I would also > add something similar to the web site. > > Note that subsequent to the release a minor source incompatibility was > found due to the

Re: 2.6 is not source compatible with 2.5

Here is the text that I propose to add to the announcement. I would also add something similar to the web site.Note that subsequent to the release a minor source incompatibility was found due to the addition of new methods tothe Logger interface. If you have code that does:logger.error(null, “This

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

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Jenkins build became unstable: Log4j 2.x #1982

See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: org.apache.logging.log4j.util.Unbox.isBoxedPrimitive(StringBuilder)

Why is it called Unbox? Seems like a misleading and confusing name when all the methods are called "box"! "Boxer" might be better. Gary On Thu, May 26, 2016 at 6:32 PM, Gary Gregory wrote: > There are no callers of the method within Log4j ATM. > > Gary > > On Thu, May

[jira] [Closed] (LOG4J2-1385) (GC) CSV layouts should not create a new CSVPrinter for each log event

[ https://issues.apache.org/jira/browse/LOG4J2-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1385. Resolution: Fixed In Git master. > (GC) CSV layouts should not create a new CSVPrinter for each

[jira] [Updated] (LOG4J2-1385) (GC) CSV layouts should not create a new CSVPrinter for each log event

[ https://issues.apache.org/jira/browse/LOG4J2-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1385: - Summary: (GC) CSV layouts should not create a new CSVPrinter for each log event (was: CSV

[jira] [Closed] (LOG4J2-1399) Update Apache Commons CSV from 1.3 to 1.4

[ https://issues.apache.org/jira/browse/LOG4J2-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1399. Resolution: Fixed Fix Version/s: 2.6.1 In Git master. > Update Apache Commons CSV from 1.3

Re: 2.6 is not source compatible with 2.5

Yet another reason to hate null! ;) On 29 May 2016 at 13:13, Ralph Goers wrote: > When you pass null as the first argument it doesn't know which is better > > Sent from my iPhone > > On May 29, 2016, at 11:07 AM, Matt Sicker wrote: > > Wait, how

Re: 2.6 is not source compatible with 2.5

When you pass null as the first argument it doesn't know which is better Sent from my iPhone > On May 29, 2016, at 11:07 AM, Matt Sicker wrote: > > Wait, how are error(Marker, String, Object) and error(String, Object, Object) > even confused by the compiler? > >> On 29 May

Re: 2.6 is not source compatible with 2.5

Only if the compatibility issue can be fixed. I don't think it can. We will just update the site and announcement. Sent from my iPhone > On May 29, 2016, at 10:56 AM, Matt Sicker wrote: > > So what do we do, follow up with 2.6.1 right away? > >> On 29 May 2016 at 12:29,

I've written a blog post about 2.6

http://musigma.org/java/log4j/2016/05/29/log4j-2.6.html Let me know what you think. I haven't blogged in a long time, but I'm starting to get back into it partly to help motivate a friend of mine to keep writing himself. -- Matt Sicker

Re: 2.6 is not source compatible with 2.5

So what do we do, follow up with 2.6.1 right away? On 29 May 2016 at 12:29, Ralph Goers wrote: > Can’t do that. That would require a re-release. > > Speaking of which, the archives directory only lists a couple of releases. > I thought they were all supposed to be

Re: 2.6 is not source compatible with 2.5

Can’t do that. That would require a re-release. Speaking of which, the archives directory only lists a couple of releases. I thought they were all supposed to be there. Ralph > On May 29, 2016, at 10:19 AM, Gary Gregory wrote: > > I think the RELEASE-NOTES.txt in the

Re: 2.6 is not source compatible with 2.5

I think the RELEASE-NOTES.txt in the dist area needs to be updated as well. Gary On Sun, May 29, 2016 at 10:15 AM, Ralph Goers wrote: > I will add something to the announcement text when I send out the emails. > Those will go out in a few hours. > > Ralph > > On May

Re: 2.6 is not source compatible with 2.5

That would be good. I try to remember to add @since everywhere I can remember to, but an automated tool would help a lot. On 29 May 2016 at 12:02, Gary Gregory wrote: > On Sun, May 29, 2016 at 9:57 AM, Gary Gregory > wrote: > >> And to make it

Re: 2.6 is not source compatible with 2.5

I will add something to the announcement text when I send out the emails. Those will go out in a few hours. Ralph > On May 29, 2016, at 9:53 AM, Gary Gregory wrote: > > We are going to need to update the release notes and/or site for 2.6 to note > that the 2.6 is not

Re: 2.6 is not source compatible with 2.5

I suspect most people would have coded logger.error(message, t) though so hopefully it won’t be too bad. Ralph > On May 29, 2016, at 9:53 AM, Gary Gregory wrote: > > We are going to need to update the release notes and/or site for 2.6 to note > that the 2.6 is not

Re: 2.6 is not source compatible with 2.5

Darn. I wish you had caught that before the vote. That is not good. Ralph > On May 29, 2016, at 10:02 AM, Gary Gregory wrote: > > On Sun, May 29, 2016 at 9:57 AM, Gary Gregory > wrote: > And to make it more

Re: Logo themes

Gary, The logo is a jpeg on the site so I had to convert the png to a jpeg so that I wouldn’t have to modify the html on every page. Not a big deal though. Ralph > On May 27, 2016, at 10:30 PM, Gary Gregory wrote: > > Here is the one logo you mentioned with a 2.6

Re: 2.6 is not source compatible with 2.5

On Sun, May 29, 2016 at 9:57 AM, Gary Gregory wrote: > And to make it more difficult to see what's changed, we do not have @since > 2.6 Javadoc markers for the new methods in Logger that expand arguments up > to 10 Objects :-( > I wonder which one of Clirr or Checkstyle

Re: 2.6 is not source compatible with 2.5

And to make it more difficult to see what's changed, we do not have @since 2.6 Javadoc markers for the new methods in Logger that expand arguments up to 10 Objects :-( Gary On Sun, May 29, 2016 at 9:53 AM, Gary Gregory wrote: > We are going to need to update the release

2.6 is not source compatible with 2.5

We are going to need to update the release notes and/or site for 2.6 to note that the 2.6 is not source compatible with previous releases. I tested going from 2.5 to 2.6 at work and got: [ERROR] COMPILATION ERROR : [INFO] - [ERROR]

[jira] [Created] (LOG4J2-1399) Update Apache Commons CSV from 1.3 to 1.4

Gary Gregory created LOG4J2-1399: Summary: Update Apache Commons CSV from 1.3 to 1.4 Key: LOG4J2-1399 URL: https://issues.apache.org/jira/browse/LOG4J2-1399 Project: Log4j 2 Issue Type:

[jira] [Updated] (LOG4J2-1385) CSV layouts should not create a new CSVPrinter for each log event

[ https://issues.apache.org/jira/browse/LOG4J2-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1385: - Fix Version/s: (was: 2.6) 2.6.1 > CSV layouts should not create a new

[jira] [Updated] (LOG4J2-1229) Error creating logger

[ https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1229: - Fix Version/s: (was: 2.6) 2.6.1 > Error creating logger >

[jira] [Updated] (LOG4J2-1086) SizeBasedTriggeringPolicy is not working properly with Logj2 2.3 version jars

[ https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1086: - Fix Version/s: (was: 2.6) 2.6.1 > SizeBasedTriggeringPolicy is not

[jira] [Updated] (LOG4J2-1130) CsvLogEventLayout NanoTime timestamp is always zero.

[ https://issues.apache.org/jira/browse/LOG4J2-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1130: - Fix Version/s: (was: 2.6) 2.6.1 > CsvLogEventLayout NanoTime timestamp is

[jira] [Updated] (LOG4J2-1116) Web app-friendly thread locals for gc-free logging (was: upgrade to log4j2 causes too frequent minor gc)

[ https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1116: - Fix Version/s: (was: 2.6) 2.6.1 > Web app-friendly thread locals for

[jira] [Updated] (LOG4J2-1198) Add support for custom rollover strategy

[ https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1198: - Fix Version/s: (was: 2.6) 2.6.1 > Add support for custom rollover

[jira] [Updated] (LOG4J2-1013) Log4j2 Main Arguments Lookup by name doesn't work

[ https://issues.apache.org/jira/browse/LOG4J2-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1013: - Fix Version/s: (was: 2.6) 2.6.1 > Log4j2 Main Arguments Lookup by name

[jira] [Updated] (LOG4J2-1381) Documentation for LoggerNameLevelRewritePolicy is wrong

[ https://issues.apache.org/jira/browse/LOG4J2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1381: - Fix Version/s: (was: 2.6) 2.6.1 > Documentation for

[jira] [Updated] (LOG4J2-915) Wrong timestamp of filename when SizeBasedTriggering and TimeBasedTrigger used simultaniously with RollingFileAppender

[ https://issues.apache.org/jira/browse/LOG4J2-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-915: Fix Version/s: (was: 2.6) 2.6.1 > Wrong timestamp of filename when

[jira] [Updated] (LOG4J2-849) [Perf] Add performance tests to compare overhead of various logging APIs

[ https://issues.apache.org/jira/browse/LOG4J2-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-849: Fix Version/s: (was: 2.6) 2.6.1 > [Perf] Add performance tests to compare

Re: [VOTE][RESULT] Log4j 2.6 rc1

Thanks for doing the release! On 29 May 2016 at 11:25, Gary Gregory wrote: > On May 29, 2016 7:01 AM, "Remko Popma" wrote: > > > > Ralph, thank you for doing the release work! > > +1 > > Gary > > > > Remko > > > > Sent from my iPhone > > > > On

Re: [VOTE][RESULT] Log4j 2.6 rc1

On May 29, 2016 7:01 AM, "Remko Popma" wrote: > > Ralph, thank you for doing the release work! +1 Gary > > Remko > > Sent from my iPhone > > On 2016/05/29, at 15:48, Ralph Goers wrote: > >> The artifacts have been released. I will update

Re: [VOTE][RESULT] Log4j 2.6 rc1

Ralph, thank you for doing the release work! Remko Sent from my iPhone > On 2016/05/29, at 15:48, Ralph Goers wrote: > > The artifacts have been released. I will update the web site in the morning. > > Ralph > >> On May 28, 2016, at 11:10 PM, Ralph Goers

[jira] [Commented] (LOG4J2-1397) Support ByteBufferLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305883#comment-15305883 ] Remko Popma commented on LOG4J2-1397: - Example no-frills implementation:

Re: [VOTE][RESULT] Log4j 2.6 rc1

The artifacts have been released. I will update the web site in the morning. Ralph > On May 28, 2016, at 11:10 PM, Ralph Goers wrote: > > The vote has passed with binding +1 votes from Remko Popma, Ralph Goers, Gary > Gregory and Matt Sicker. Mikael Ståldal also

[VOTE][RESULT] Log4j 2.6 rc1

The vote has passed with binding +1 votes from Remko Popma, Ralph Goers, Gary Gregory and Matt Sicker. Mikael Ståldal also cast a +1 vote. Thanks to all who voted. I will continue on with the release process. Ralph