[GitHub] logging-log4j2 issue #92: Consider the StringBuilder's capacity instead of c...

Github user xnslong commented on the issue: https://github.com/apache/logging-log4j2/pull/92 I runned this test, but it didn't fail on my machine. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not h

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092624#comment-16092624 ] Ajitha commented on LOG4J2-1921: Can you guide me how to pull it via gradle? > Getting C

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092605#comment-16092605 ] Ralph Goers commented on LOG4J2-1921: - I created a branch named "android" which has a

[jira] [Comment Edited] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092598#comment-16092598 ] Ajitha edited comment on LOG4J2-1921 at 7/19/17 5:28 AM: - Is ther

[jira] [Commented] (LOG4J2-1921) Getting ClassCastException while getting LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092598#comment-16092598 ] Ajitha commented on LOG4J2-1921: Is there a update on this? Can you please find a way to

Jenkins build is unstable: Log4j 2.x #2916

See

Re: [log4net] ci pipeline status update

On 2017-07-18, Dominik Psenner wrote: > oohh how I like to be the bringer of good news! Right now I was finally > able to fix the building of the netstandard target by providing a > jenkinsfile script that detects the UID and GID of the working path and > passing that in as parameters into the bui

Build failed in Jenkins: Log4j 2.x #2914

See Changes: [ggregory] Slightly better internal logging. -- [...truncated 1.06 MB...] [INFO] Building jar:

Build failed in Jenkins: Log4j 2.x #2913

See -- [...truncated 1.05 MB...] [INFO] Building jar: [INFO] [INFO] --- maven-install-

Build failed in Jenkins: Log4j 2.x #2912

See Changes: [ggregory] Refactor a touch for reuse and customization. [ggregory] Refactor a touch for reuse and customization. -- [...truncated 1.06 MB...] [INFO] Building jar

[GitHub] logging-log4j2 issue #93: modification to resolver to discover jar assests w...

Github user garydgregory commented on the issue: https://github.com/apache/logging-log4j2/pull/93 Hi. Were you able to create a sample jar for testing? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

Build failed in Jenkins: Log4j 2.x #2911

See Changes: [ggregory] Update sample tool chain file with current release. -- [...truncated 1.05 MB...] [INFO] Building jar:

Build failed in Jenkins: Log4j 2.x #2910

See Changes: [ggregory] Add -- [...truncated 1.07 MB...] [INFO] Building jar:

[jira] [Assigned] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1883: --- Assignee: Remko Popma > Timestamp does not seem to support microseconds level >

Build failed in Jenkins: Log4j 2.x #2909

See Changes: [ggregory] More precise name for lastModified -> lastModifiedMillis. -- [...truncated 1.05 MB...] [INFO] Building jar:

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092387#comment-16092387 ] Remko Popma commented on LOG4J2-1883: - [~garydgregory] This JIRA ticket is not about

Build failed in Jenkins: Log4j 2.x #2908

See Changes: [ggregory] Slightly better Javadoc. -- [...truncated 1.05 MB...] [INFO] Building jar:

[jira] [Comment Edited] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092220#comment-16092220 ] Gary Gregory edited comment on LOG4J2-1883 at 7/18/17 9:33 PM:

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092220#comment-16092220 ] Gary Gregory commented on LOG4J2-1883: -- I really hope we can move to Java 8 BEFORE J

Re: [log4net] ci pipeline status update

Hi, oohh how I like to be the bringer of good news! Right now I was finally able to fix the building of the netstandard target by providing a jenkinsfile script that detects the UID and GID of the working path and passing that in as parameters into the builder-netstandard dockerfile when it is bui

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092087#comment-16092087 ] Anthony Maire commented on LOG4J2-1883: --- [~_chandra] : You're perfectly right about

Build failed in Jenkins: log4net-trunk-tests #113

See Changes: [dpsenner] builder-netstandard: attempt to pass in the uid and gid of jenkins as [dpsenner] Jenkinsfile: another attempt to set jenkins_uid and jenkins_gid [dpsenner] Jenkinsfile: yet another att

[jira] [Comment Edited] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091963#comment-16091963 ] Ralph Goers edited comment on LOG4J2-1883 at 7/18/17 6:32 PM: -

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091963#comment-16091963 ] Ralph Goers commented on LOG4J2-1883: - If we wanted to go the the trouble to create o

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091876#comment-16091876 ] Gary Gregory commented on LOG4J2-1883: -- Once we make Java 8 the platform requirement

How to unsubscribe?

Please help me to unsubscribe the mailing list!Sending to dev-unsubscribe simply doesn't work.WOd: "chandra (JIRA)" Do: dev@logging.apache.org; Wysłane: 17:50 Wtorek 2017-07-18Temat: [jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level> >

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091742#comment-16091742 ] chandra commented on LOG4J2-1883: - Although, it's nice to maintain a nanosecond level acc

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091710#comment-16091710 ] Anthony Maire commented on LOG4J2-1883: --- - Joda Time Instant has a millisecond gran

[jira] [Commented] (LOGCXX-490) conditional expression is constant

[ https://issues.apache.org/jira/browse/LOGCXX-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091706#comment-16091706 ] Sebastian Geiger commented on LOGCXX-490: - As I understand this issue is fixed in

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091690#comment-16091690 ] Matt Sicker commented on LOG4J2-1883: - The issue at hand is that Java does not expose

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091685#comment-16091685 ] Gary Gregory commented on LOG4J2-1883: -- Hm... maybe Joda-Time will not help here. Ja

Re: Build failed in Jenkins: Log4j 2.x #2907

I think Remko is right. It'd be nice if it gave a more useful error like invalid class file format or something, though, to be sure. On 18 July 2017 at 07:09, Remko Popma wrote: > I think compilation fails because the class version is incompatible: we're > using the 1.7 javac to compile but use

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091675#comment-16091675 ] Gary Gregory commented on LOG4J2-1883: -- Using an Instant on Java 8 would do the tric

[jira] [Commented] (LOGCXX-490) conditional expression is constant

[ https://issues.apache.org/jira/browse/LOGCXX-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091494#comment-16091494 ] Thorsten Schöning commented on LOGCXX-490: -- Have a look at the head of logger.h,

Re: Build failed in Jenkins: Log4j 2.x #2907

I think compilation fails because the class version is incompatible: we're using the 1.7 javac to compile but use the 1.8 jconsole jar as a compilation dependency. (Shameless plug) Every java main() method deserves http://picocli.info > On Jul 18, 2017, at 15:26, Gary Gregory wrote: > > Beca

[jira] [Commented] (LOGCXX-490) conditional expression is constant

[ https://issues.apache.org/jira/browse/LOGCXX-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091458#comment-16091458 ] Sebastian Geiger commented on LOGCXX-490: - Hi, using `while(!true)` gives the sam

[jira] [Commented] (LOGCXX-490) conditional expression is constant

[ https://issues.apache.org/jira/browse/LOGCXX-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091395#comment-16091395 ] Thorsten Schöning commented on LOGCXX-490: -- This is what MS says about the warnin

Re: Lilith and Log4j 2

A general event header and footer would probably be overkill. I’m using the following interface in Lilith: public interface WriteByteStrategy {     void writeBytes(DataOutputStream dataOutputStream, byte[] bytes)         throws IOException; } One implementation writes an int with the length of b

[jira] [Created] (LOGCXX-490) conditional expression is constant

Sebastian Geiger created LOGCXX-490: --- Summary: conditional expression is constant Key: LOGCXX-490 URL: https://issues.apache.org/jira/browse/LOGCXX-490 Project: Log4cxx Issue Type: Improvem

Mailinglist links are outdated.

The links at https://logging.apache.org/log4j/2.x/mail-lists.html are still pointing to the old mailinglists. Just realized while trying to sign up with this email address.

[log4net] jenkins build fails with a stacktrace

Hi, Now that master is back online I've attempted to run the jenkins pipeline but it failed with a stacktrace: https://builds.apache.org/job/logging-log4net/job/feature%252Fcd-pipeline/131/console FYI, I reported this to INFRA: https://issues.apache.org/jira/browse/INFRA-14628 Cheers -- Domin

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091212#comment-16091212 ] Anthony Maire commented on LOG4J2-1883: --- The code is running on Java 7, but you're