was included in the changelog and fixed some more in
2.8.1.
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
>
like Clirr which looks mostly dead, and
not in the Princess Bride sense.
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
>
t to always/only run the build on Java 8. The
point is to make it possible to run on Java 8.
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
>
i in LOG4J2-1576. Why did you decide on
japicmp?
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
> Project: Log4j 2
>
in Apache Commons.
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
> Project: Log4j 2
> Issue Type: Improvement
>
ll will want to use the minimum
Java version to build the release.
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
> Project: Log4j
r, I still will want to use the minimum
Java version to build the release.
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
>
[
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 Jav
ledge of Log4j internals.
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
> Key: LOG4J2-1636
>
uild 136
{code:java}
setOut0(newPrintStream(fdOut, props.getProperty("sun.stdout.encoding")));
setErr0(newPrintStream(fdErr, props.getProperty("sun.stderr.encoding")));
{code}
> Console Appender does not pick up Oracle Java 8's sun.stdout.enc
, this is backwards incompatible. Add an option to disable this behavior.
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
>
. Add an option to disable this behavior.)
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
> Key: LOG4J2-1636
>
, this is backwards incompatible. Add an option to disable this behavior.
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
>
G4J2-1630 - namely, allowing a
configuration element to locate its parent.
Did you happen to check to see what Java 9 does?
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.
what {{sun.stdout.encoding}} says?
I'm not sure how to solve this cleanly.
Suggestions welcome.
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
>
Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
> Key: LOG4J2-1636
> URL: https://issu
t on your pattern layout if that is the
layout you are indeed using... like {{$\{sys:sun.stdout.encoding}}}
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
>
like ${sys:sun.stdout.encoding}
> Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
> Key: LOG4J2-1636
>
Console Appender does not pick up Oracle Java 8's sun.stdout.encoding and
> sun.stderr.encoding
> --
>
> Key: LOG4J2-1636
> URL: https://issues.apache.
[
https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1636:
-
Description:
The Oracle Java 8 platform supports two system properties to configure the
System
[
https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1636:
-
Summary: Console Appender does not pick up Oracle Java 8's
sun.stdout.encodin
[
https://issues.apache.org/jira/browse/LOG4J2-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1636:
-
Summary: Console Appender does not pick up Oracle Java 8's (was: Bad
console output enc
ives.
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
> Project: Log4j 2
> Issue Type: Improvement
>
urse. Apache Commons BeanUtils uses one. Now
that BCEL 6.0 is out, Clirr should pick it up but development on Clirr looks
dead. Then the Maven plugin would need to pick up the Clirr. IOW, it does not
look good.
> Build process should work on
cess to Java 8 until we drop support
for Java 7.
> Build process should work on Java 8
> ---
>
> Key: LOG4J2-1587
> URL: https://issues.apache.org/jira/browse/LOG4J2-1587
> Project: Log4j 2
>
[
https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-1587:
---
Description:
The whole Maven build process, including {{site}}, should work on Java 8 (as
Mikael Ståldal created LOG4J2-1587:
--
Summary: Build process should work on Java 8
Key: LOG4J2-1587
URL: https://issues.apache.org/jira/browse/LOG4J2-1587
Project: Log4j 2
Issue Type
[
https://issues.apache.org/jira/browse/LOG4J2-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker closed LOG4J2-863.
--
Resolution: Fixed
We're on findbugs 3.0.3 currently and Java 7, I build with Java 8 all the
[
https://issues.apache.org/jira/browse/LOG4J2-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1151:
Description:
Java 8 made large improvements to String encoding performance for all character
sets
[
https://issues.apache.org/jira/browse/LOG4J2-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-854.
--
No, I think the javadoc looks great now.
I'm closing this issue.
> Use java 8 doclet to genera
sing Java 8 to generate the site?
> Use java 8 doclet to generate log4j Javadoc
>
>
> Key: LOG4J2-854
> URL: https://issues.apache.org/jira/browse/LOG4J2-854
> Project: Log4j 2
>
Ralph has mentioned running the whole build on a
single JDK for now.
Once we switch to Java 8 that will be moot. When that will be is... not for a
while I am guessing.
> Use java 8 doclet to generate log4j Javadoc
>
>
>
the Javadoc generated with Java 6, I
thought this was done.
Reopen?
> Use java 8 doclet to generate log4j Javadoc
>
>
> Key: LOG4J2-854
> URL: https://issues.apache.org/jira/browse/LOG4J2-854
>
rate the site.
> Use java 8 doclet to generate log4j Javadoc
>
>
> Key: LOG4J2-854
> URL: https://issues.apache.org/jira/browse/LOG4J2-854
> Project: Log4j 2
>
[
https://issues.apache.org/jira/browse/LOG4J2-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-854.
Resolution: Fixed
Fix Version/s: 2.5
> Use java 8 doclet to generate log4j Java
- on Java 7, use JDK 8 backported logic to handle invalid input
- layout manual documentation improvement
> Performance improvement: backport fast Java 8 ISO-8859-1 String to byte[]
> encoder to AbstractString
ple 143561 316.768 ± 3.482 ns/op
{code}
> Performance improvement: backport fast Java 8 ISO-8859-1 String to byte[]
> encoder to AbstractStringLayout
> -
>
> Key: LOG4J2
1445. Also mentioned this change in Layout
manual page.
> Performance improvement: backport fast Java 8 ISO-8859-1 String to byte[]
> encoder to AbstractStringLayout
> -
>
>
g chars to
bytes will give incorrect results. For now I am changing the check to include
US-ASCII.
> Performance improvement: backport fast Java 8 ISO-8859-1 String to byte[]
> encoder to Abstrac
[
https://issues.apache.org/jira/browse/LOG4J2-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1151:
Summary: Performance improvement: backport fast Java 8 ISO-8859-1 String to
byte[] encoder to
[
https://issues.apache.org/jira/browse/LOG4J2-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma reopened LOG4J2-1151:
-
> Performance improvement: backport fast Java 8 String to byte[] encoder to
> AbstractString
logging-log4j2 git commit: LOG4J2-1151 Performance improvement:
backport fast Java 8 String to byte[] encoder to AbstractStringLayout.
Repository: logging-log4j2
Updated Branches:
refs/heads/master f8700e721 -> aabd21883
LOG4J2-1151 Performance improvement: backport fast Java 8 Str
[
https://issues.apache.org/jira/browse/LOG4J2-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-1151.
---
> Performance improvement: backport fast Java 8 String to byte[] encoder to
> AbstractString
ast Java 8 String to byte[] encoder to
> AbstractStringLayout
> --
>
> Key: LOG4J2-1151
> URL: https://issues.apache.org/jira/browse/LOG4J2-1151
>
[
https://issues.apache.org/jira/browse/LOG4J2-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1151:
Description:
Java 8 made large improvements to String encoding performance for all character
sets
Remko Popma created LOG4J2-1151:
---
Summary: Performance improvement: backport fast Java 8 String to
byte[] encoder to AbstractStringLayout
Key: LOG4J2-1151
URL: https://issues.apache.org/jira/browse/LOG4J2-1151
I plan on building the release with Java 7. I will give the site build a shot
with Java 8 and see how it comes out. I am hopeful I can do the 2.4 release
over the holiday weekend.
Ralph
> On Jun 30, 2015, at 8:51 AM, Gary Gregory wrote:
>
> Well, it's all at the RM's
;>> I also like the java8 Javadoc though.
>>>
>>> Sent from my iPhone
>>>
>>> On 2015/06/30, at 8:38, Ralph Goers wrote:
>>>
>>> That would be the site build. I always build the artifacts with the idk
>>> we are targ
ing just to be safe.
>>
>> Ralph
>>
>> On Jun 29, 2015, at 4:24 PM, Gary Gregory wrote:
>>
>> Mostly to RG: Any thoughts on building with Java 8 to get the nicer
>> looking Javadocs?
>>
>> Gary
>>
>> --
>> E-Mail: garydgreg...@gm
>
> On Jun 29, 2015, at 4:24 PM, Gary Gregory wrote:
>
> Mostly to RG: Any thoughts on building with Java 8 to get the nicer
> looking Javadocs?
>
> Gary
>
> --
> E-Mail: [email protected] | [email protected]
> Java Persistence with Hibernate, Seco
; That would be the site build. I always build the artifacts with the idk we
> are targeting just to be safe.
>
> Ralph
>
>> On Jun 29, 2015, at 4:24 PM, Gary Gregory wrote:
>>
>> Mostly to RG: Any thoughts on building with Java 8 to get the nicer looking
>>
That would be the site build. I always build the artifacts with the idk we are
targeting just to be safe.
Ralph
> On Jun 29, 2015, at 4:24 PM, Gary Gregory wrote:
>
> Mostly to RG: Any thoughts on building with Java 8 to get the nicer looking
> Javadocs?
>
> Gary
Mostly to RG: Any thoughts on building with Java 8 to get the nicer looking
Javadocs?
Gary
--
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com
[
https://issues.apache.org/jira/browse/LOG4J2-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-854:
---
Affects Version/s: 2.1
> Use java 8 doclet to generate log4j Java
[
https://issues.apache.org/jira/browse/LOG4J2-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-854:
---
Fix Version/s: (was: 2.1)
> Use java 8 doclet to generate log4j Java
does that mean that you then need to invoke it specifically with the
> -P option?
>
> Gary
>
>
>>
>> -- Forwarded message --
>> From:
>> Date: 29 September 2014 09:28
>> Subject: git commit: Use a Maven profile to activat
And I updated the profile ID like I mentioned earlier.
On 29 September 2014 12:27, Gary Gregory wrote:
> I added a Maven profile that automatically picks up FindBugs 3.0.0 on Java
> 8.
>
> Gary
>
> On Mon, Sep 29, 2014 at 12:16 AM, Remko Popma
> wrote:
>
I added a Maven profile that automatically picks up FindBugs 3.0.0 on Java
8.
Gary
On Mon, Sep 29, 2014 at 12:16 AM, Remko Popma wrote:
> It seems to choke on ConcurrentHashMap.
>
> Unable to get XClass for java/util/concurrent/ConcurrentHashMap
>
> Can we exclude the JDK classe
; Subject: git commit: Use a Maven profile to activate FindBugs 3.0.0 only
> on Java 8.
> To: [email protected]
>
>
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master 1201fa3d6 -> 630aea837
>
>
> Use a Maven profile to activate Find
This could use a profile id like jdk8.
-- Forwarded message --
From:
Date: 29 September 2014 09:28
Subject: git commit: Use a Maven profile to activate FindBugs 3.0.0 only on
Java 8.
To: [email protected]
Repository: logging-log4j2
Updated Branches:
refs/heads/master
[
https://issues.apache.org/jira/browse/LOG4J2-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-863:
Description: The build fails on Java 8 due to FindBugs 2.x blowing up.
FindBugs 3.0.0 solves the
Gary Gregory created LOG4J2-863:
---
Summary: FindBugs build fails on Java 8
Key: LOG4J2-863
URL: https://issues.apache.org/jira/browse/LOG4J2-863
Project: Log4j 2
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LOG4J2-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-680.
-
Resolution: Fixed
> Javadocs build fails on Jav
[
https://issues.apache.org/jira/browse/LOG4J2-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-680:
Summary: Javadocs build fails on Java 8 (was: Build fails on Java 8)
> Javadocs build fails
ilding on Java 8 to get the nice Javadoc
> output but building on Java 8 does not work. See below. Can anyone build on
> Java 8?
>
> Updating to FindBugs3.0.0 fixes the problem below but would require Java 7 to
> build the site. Unless some special Maven magic is created i
I know Matt has been talking about building on Java 8 to get the nice
Javadoc output but building on Java 8 does not work. See below. Can anyone
build on Java 8?
Updating to FindBugs3.0.0 fixes the problem below but would require Java 7
to build the site. Unless some special Maven magic is
Remko Popma created LOG4J2-854:
--
Summary: Use java 8 doclet to generate log4j Javadoc
Key: LOG4J2-854
URL: https://issues.apache.org/jira/browse/LOG4J2-854
Project: Log4j 2
Issue Type
far.
> Build fails on Java 8
> -
>
> Key: LOG4J2-680
> URL: https://issues.apache.org/jira/browse/LOG4J2-680
> Project: Log4j 2
> Issue Type: Bug
> Env
[
https://issues.apache.org/jira/browse/LOG4J2-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-680:
---
Labels: Java8 javadoc (was: )
> Build fails on Jav
Gary Gregory created LOG4J2-680:
---
Summary: Build fails on Java 8
Key: LOG4J2-680
URL: https://issues.apache.org/jira/browse/LOG4J2-680
Project: Log4j 2
Issue Type: Bug
Environment
FWIW, there are going to be a likely pile of Javadoc errors if you try to
build with Java 8 due to Javadoc's stricter doclint. IOW, HTML in Javadoc
really should be XHTML.
Gary
--
E-Mail: [email protected] | [email protected]
Java Persistence with Hibernate, Second Edition
[
https://issues.apache.org/jira/browse/LOG4J2-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker closed LOG4J2-560.
--
Verified working in my Java 8 environment now.
> TLSSyslogAppenderTest is failing in trunk with Jav
1574267. Please verify and close.
> TLSSyslogAppenderTest is failing in trunk with Java 8 (build 1.8.0-b128)
>
>
> Key: LOG4J2-560
> URL: https://issues.apache.org/jira/br
how the Structured Data elements
are being written has changed. I'll have to look some more to figure out why.
> TLSSyslogAppenderTest is failing in trunk with Java 8 (build 1.8.0-b128)
>
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920075#comment-13920075
]
Ralph Goers commented on LOG4J2-560:
I installed Java 8 and am seeing the
4 PM:
I'm on OSX. Just noticed that I'm also using Java 1.8. So I guess it really is
related to Java 8.
mvn -version
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.8.0, vendor: Orac
7;m also using Java 1.8. So I guess it really is
related to Java 8.
> TLSSyslogAppenderTest is failing in trunk with Java 8 (build 1.8.0-b128)
>
>
> Key: LOG4J2-560
> URL: https://
[
https://issues.apache.org/jira/browse/LOG4J2-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-560:
Summary: TLSSyslogAppenderTest is failing in trunk with Java 8 (build
1.8.0-b128) (was
[
https://issues.apache.org/jira/browse/LOG4J2-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-560:
Environment: Maven, IntelliJ, Java 8 (build 1.8.0-b128) (was: Maven,
IntelliJ
[
https://issues.apache.org/jira/browse/LOG4J2-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-560:
Summary: TLSSyslogAppenderTest is failing in trunk with Java 8 (was:
TLSSyslogAppenderTest is
[
https://issues.apache.org/jira/browse/LOG4J2-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-560:
Environment:
Maven, IntelliJ, Java 8 (build 1.8.0-b128)
Apache Maven 3.2.1
, we found that a deprecated
library developed by use put a beta4 jar on the release class path.
Nevertheless until we found that, we could even reproduced it under Linux.
Thanks for your effort, and sorry for the false report.
> EmptyStackException when logging exceptions with Log4J2 in
Java 1.7.0_45 or Java 8 on my Mac. Are you sure
that you have deleted ALL beta4 JARs and replaced them with beta9 JARs?
> EmptyStackException when logging exceptions with Log4J2 in Java 8
> -
>
>
gain Java 6 doesn't expose this behavior.
> EmptyStackException when logging exceptions with Log4J2 in Java 8
> -
>
> Key: LOG4J2-245
> URL: https://issues.apache.org/jira/browse/LO
the EmptyStackException in Java 8. In theory
this issue can be closed, unless you want to leave it open as a reminder to
look for Java 8 alternatives to getCallerClass at a later date.
> EmptyStackException when logging exceptions with Log4J2 in
revision 1481671. I also added a
check for a single parameter to getCallerClass so it will not be found in Java
8. I have not found an equivalent replacement in Java 8 yet.
> EmptyStackException when logging exceptions with Log4J2 in Jav
out that this problem will happen unconditionally when logging a
Throwable on a Java 8 JVM.]
Possibly affects earlier versions, too, but I did not check.
beta5 and beta6 are both unusable with Spring Framework. Any time an error gets
logged through log4j-jcl bridge using Spring, the error below
87 matches
Mail list logo
