Just to play devil's advocate... I'm not so sure on the laggard view. If I
start a new project today, it is a Java 8 project or maybe a java 7 project if
some kit breaks on 8. For my major existing project that recently moved from
java 6 to 7, I gave up upgrading from log4j 1 to 2 because we dep
We have had this discussion before. There are some components that should be
leaders and some that should be laggards when it comes to upgrading. My
opinion is that Log4j needs to be at the tail end in terms of dropping support
for older Java versions.
Ralph
> On Nov 30, 2014, at 11:05 PM, Ga
I suppose that is one way to do it. Perhaps a better way would be to call
MarkerManager.clear() at the beginning and end of both LoggerTest and
MarkerTest.
Ralph
> On Nov 30, 2014, at 10:57 PM, ggreg...@apache.org wrote:
>
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master
Hm, one of those blog shows Java 7 ~ 80 % and Java 6 at ~20 %. That fits
the general 80/20 rule for me ;-)
Gary
On Mon, Dec 1, 2014 at 12:58 AM, Ralph Goers
wrote:
> Or, I guess, when one of these surveys shows Java 6 is down below 10%.
> Neither of these is extremely current, but it is interes
That makes sense. Both declare a Marker with the same name but with different
parents. Now that I know what is causing it I think I can fix it.
Ralph
> On Nov 30, 2014, at 10:42 PM, Gary Gregory wrote:
>
> This can be reproduced by running the LoggerTest before the MarkerTest:
>
> cd log4j-s
Minecraft! ;-)
On Mon, Dec 1, 2014 at 12:58 AM, Ralph Goers
wrote:
> Or, I guess, when one of these surveys shows Java 6 is down below 10%.
> Neither of these is extremely current, but it is interesting to note that
> the second showed Java 6’s usage actually increase over the last several
> mon
Or, I guess, when one of these surveys shows Java 6 is down below 10%. Neither
of these is extremely current, but it is interesting to note that the second
showed Java 6’s usage actually increase over the last several months. I can’t
imagine why that would be.
http://adtmag.com/blogs/watersworks
Should be fixed in git master now.
Gary
On Mon, Dec 1, 2014 at 12:51 AM, Gary Gregory
wrote:
> You can also reproduce it this way:
>
> package org.apache.logging.slf4j;
>
> import org.junit.runner.RunWith;
> import org.junit.runners.Suite;
> import org.junit.runners.Suite.SuiteClasses;
>
> @Run
You can also reproduce it this way:
package org.apache.logging.slf4j;
import org.junit.runner.RunWith;
import org.junit.runners.Suite;
import org.junit.runners.Suite.SuiteClasses;
@RunWith(Suite.class)
@SuiteClasses({
LoggerTest.class,
MarkerTest.class })
public class OrderBugTes
On Mon, Dec 1, 2014 at 12:44 AM, Gary Gregory
wrote:
> The brute force way to 'fix' this is to set reuseForks to false in the
> parent POM but then we will never find leaky kinds of bugs.
>
Oh, and that would slow down the test phase a lot.
Gary
>
> Gary
>
> On Mon, Dec 1, 2014 at 12:42 AM, Ga
The brute force way to 'fix' this is to set reuseForks to false in the
parent POM but then we will never find leaky kinds of bugs.
Gary
On Mon, Dec 1, 2014 at 12:42 AM, Gary Gregory
wrote:
> This can be reproduced by running the LoggerTest before the MarkerTest:
>
> cd log4j-slf4j-impl
> mvn te
This can be reproduced by running the LoggerTest before the MarkerTest:
cd log4j-slf4j-impl
mvn test
-Dtest=org.apache.logging.slf4j.LoggerTest,org.apache.logging.slf4j.MarkerTest
Gary
On Sat, Nov 29, 2014 at 12:16 PM, Gary Gregory
wrote:
> I see this locally. It seems that a lot of tests do n
November 2015.
Ralph
> On Nov 30, 2014, at 10:12 PM, Gary Gregory wrote:
>
> I just had to do some refactoring to account for not being able to use a Java
> 7 multi-catch.
>
> I would be OK to release 2.2 ASAP and then make Java 7 the minimum to take
> advantage to Java 7 features like mult
[
https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-834.
-
Resolution: Fixed
In git master and SNAPSHOT repo.
> ThrowableProxy throws NoClassDefFoundError
>
[
https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-834:
Summary: ThrowableProxy throws NoClassDefFoundError (was:
NoClassDefFoundError in ThrowableProxy)
[
https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229423#comment-14229423
]
Gary Gregory edited comment on LOG4J2-834 at 12/1/14 5:18 AM:
--
I just had to do some refactoring to account for not being able to use a
Java 7 multi-catch.
I would be OK to release 2.2 ASAP and then make Java 7 the minimum to take
advantage to Java 7 features like multi-catch and try-with resources.
Thoughts?
Gary
--
E-Mail: garydgreg...@gmail.com | ggreg
[
https://issues.apache.org/jira/browse/LOG4J2-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory reopened LOG4J2-834:
-
Assignee: Gary Gregory
Not fixed yet.
> NoClassDefFoundError in ThrowableProxy
> --
hi all,
Does anybody have any recommendation for longing to one appender or two; one
would be easy to read for humans, the other one would be easy to query.
Gary
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229143#comment-14229143
]
Ralph Goers edited comment on LOG4J2-909 at 11/30/14 3:54 PM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229143#comment-14229143
]
Ralph Goers commented on LOG4J2-909:
I wouldn't be that quick. If there is a bug in t
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229118#comment-14229118
]
Gary Gregory commented on LOG4J2-909:
-
So can we close this as won't fix?
> StatusLog
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229111#comment-14229111
]
Remko Popma commented on LOG4J2-909:
Behrooz, glad to see you found the {{log4j2.disab
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Behrooz Nobakht updated LOG4J2-909:
---
Description:
I have started to see the following stack track after an upgrade to the
mentione
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229088#comment-14229088
]
Behrooz Nobakht commented on LOG4J2-909:
Confirm that
{code:java}
System.setProp
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229086#comment-14229086
]
Behrooz Nobakht commented on LOG4J2-909:
Interesting enough, the same error also i
[
https://issues.apache.org/jira/browse/LOG4J2-909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Behrooz Nobakht updated LOG4J2-909:
---
Description:
I have started to see the following stack track after an upgrade to the
mentione
Behrooz Nobakht created LOG4J2-909:
--
Summary: StatusLogger Could not reconfigure JMX
java.lang.NoClassDefFoundError: sun/management/ExtendedPlatformComponent
Key: LOG4J2-909
URL: https://issues.apache.org/jira/br
The Buildbot has detected a new failure on builder log4j2-nightly while
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/log4j2-nightly/builds/178
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: lares_ubuntu
Build Reason: The Nightly schedul
29 matches
Mail list logo
