Hello Gary,
What I meant by mandatory is that the only way of getting the fix was
upgrading to 2.1. I have code freeze on Thursday so I was trying to avoid a
last minute dependency change, but it seems like that's just the way it is.
Of course I can always fork the project but that seems overkill
Good, I am glad the current version work for you.
Why would it be mandatory to upgrade? Only you can decide that ;-) The
released versions will live in the Maven repository "forever".
That part of the code was probably changed as part of fixing LOG4J2-832.
Gary
On Tue, Dec 2, 2014 at 1:16 PM, M
It would also help to see the stack trace being logged.
Gary
On Tue, Dec 2, 2014 at 1:07 PM, Gary Gregory wrote:
> FYI: the stack trace does not match with our current git master level
> sources which is not surprising since we are evolving and fixing things.
>
> If you had a little program tha
Hello Gary,
Thank you for your response. 2.1 does fix the issue, is it mandatory to
upgrade? was it a logic error or just some setting I could force into my
current version?
Thanks
On Tue, Dec 2, 2014 at 3:07 PM, Gary Gregory wrote:
> FYI: the stack trace does not match with our current git ma
FYI: the stack trace does not match with our current git master level
sources which is not surprising since we are evolving and fixing things.
If you had a little program that could reproduce the issue that would be
great.
You can also use a 2.2-SNAPSHOT from the Apache snapshot repo (or build
fr
Can you try version 2.1?
Gary
On Tue, Dec 2, 2014 at 12:46 PM, Mariano Gonzalez <
[email protected]> wrote:
> Hello,
>
> I'm progamatically creating an appender with the following code:
>
> private static final String PATTERN_LAYOUT = "%-5p %d [%t] %c: %m%n";
>
> private RollingFileAp
