Re: logging-log4j repositories

Then you just have a project based on only one of the modules in the repo, should be fine, no? On Sun, Nov 13, 2016 at 1:12 PM, Gary Gregory wrote: > From a dev POV, it's not great to pull from one repo that has all these > various language bindings. > > Gary > > On Nov 12, 2016 6:44 PM, "Re

Re: logging-log4j repositories

>From a dev POV, it's not great to pull from one repo that has all these various language bindings. Gary On Nov 12, 2016 6:44 PM, "Remko Popma" wrote: > What do you mean, pick up? Are you talking from a user's point of view > about the distribution, or from a developer's POV about your workspac

Jenkins build became unstable: Log4j 2.x #2466

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

Re: logging-log4j repositories

What do you mean, pick up? Are you talking from a user's point of view about the distribution, or from a developer's POV about your workspace? Sent from my iPhone > On 13 Nov 2016, at 11:10, Gary Gregory wrote: > > Hm, on 2nd though I'm not sure if I'd want to pick up all JVM lang updates if

Scala repo

Now that we have a populated Scala repo, shall we remove the Scala modules from the main repo? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

[jira] [Updated] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1699: - Summary: Configurable Log File Permissions with PosixFilePermission (was: Configurable Log File

Re: logging-log4j repositories

Hm, on 2nd though I'm not sure if I'd want to pick up all JVM lang updates if I only care about one... Gary On Nov 12, 2016 6:08 PM, "Gary Gregory" wrote: > I like that much better... log4j-jvm instead of jvmlang I think. > > Gary > > On Nov 12, 2016 6:00 PM, "Remko Popma" wrote: > > > > Looki

Re: logging-log4j repositories

I like that much better... log4j-jvm instead of jvmlang I think. Gary On Nov 12, 2016 6:00 PM, "Remko Popma" wrote: > > Looking at LOG4J2-1705, I was thinking that requiring a separate repository for each language could increase the barrier to entry for ideas like that. > > Would it be a good id

[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660665#comment-15660665 ] Demetrios Dimatos commented on LOG4J2-1699: --- Thanks Gary!!! > Configurable Log

logging-log4j repositories

Looking at LOG4J2-1705 , I was thinking that requiring a separate repository for each language could increase the barrier to entry for ideas like that. Would it be a good idea to create a single repository (logging-log4j-jvmlang?) which would hold

Re: builds@a.o is so sloooooooow

I created some infra tickets for travis and coveralls already. G On Nov 12, 2016 5:34 PM, "Matt Sicker" wrote: > I got us partially set up on coveralls before, but we need to add some > config stuff to the jenkins profile to run it properly. Otherwise, it'd > probably be easier to integrate wit

Re: builds@a.o is so sloooooooow

I got us partially set up on coveralls before, but we need to add some config stuff to the jenkins profile to run it properly. Otherwise, it'd probably be easier to integrate with travis. I'd support a trial of travis+coveralls. On 12 November 2016 at 02:11, Gary Gregory wrote: > It is a code co

[jira] [Commented] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API

[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660626#comment-15660626 ] Gary Gregory commented on LOG4J2-1705: -- Sure, go for it. This will be in a new repo

[jira] [Resolved] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1685. -- Resolution: Fixed Assignee: Gary Gregory (was: Mikael Ståldal) Patch merged in Git maste

Re: String advertiseURI

I believe Scott Deboy did this work for Chainsaw. We'll have to ask him. Sent from my iPhone > On 13 Nov 2016, at 2:11, Gary Gregory wrote: > > We have a bunch of appenders with "String advertiseURI". Why is this not > coded up as a java.net.URI? > > Gary > > -- > E-Mail: garydgreg...@gmai

[jira] [Created] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API

Raman Gupta created LOG4J2-1705: --- Summary: Kotlin wrapper for Log4j 2 API Key: LOG4J2-1705 URL: https://issues.apache.org/jira/browse/LOG4J2-1705 Project: Log4j 2 Issue Type: New Feature

[jira] [Commented] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660248#comment-15660248 ] Raman Gupta commented on LOG4J2-1685: - Sorry for the delay... in addition to the item

[jira] [Commented] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660030#comment-15660030 ] Raman Gupta commented on LOG4J2-1685: - Oops, hang on, still getting some errors. Chec

[jira] [Commented] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15660025#comment-15660025 ] Raman Gupta commented on LOG4J2-1685: - Apologies, `mvn clean test -pl !log4j-osgi` co

[jira] [Comment Edited] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659998#comment-15659998 ] Gary Gregory edited comment on LOG4J2-1685 at 11/12/16 6:08 PM: ---

[jira] [Commented] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659998#comment-15659998 ] Gary Gregory commented on LOG4J2-1685: -- I applied the patch to Git master with {{git

String advertiseURI

We have a bunch of appenders with "String advertiseURI". Why is this not coded up as a java.net.URI? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

[jira] [Comment Edited] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659849#comment-15659849 ] Raman Gupta edited comment on LOG4J2-1685 at 11/12/16 3:53 PM:

[jira] [Commented] (LOG4J2-1685) Single property to disable all color output

[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659849#comment-15659849 ] Raman Gupta commented on LOG4J2-1685: - Ok [~garydgregory] and [~mikaelstaldal] : I ha

[jira] [Closed] (LOG4J2-1704) Add a Builder to RollingRandomAccessFileAppender and deprecate RollingRandomAccessFileAppender.createAppender()

[ https://issues.apache.org/jira/browse/LOG4J2-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1704. Resolution: Fixed In Git master. > Add a Builder to RollingRandomAccessFileAppender and deprecate

[jira] [Updated] (LOG4J2-1704) Add a Builder to RollingRandomAccessFileAppender and deprecate RollingRandomAccessFileAppender.createAppender()

[ https://issues.apache.org/jira/browse/LOG4J2-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1704: - Description: Add a {{Builder}} to {{RollingRandomAccessFileAppender}} and deprecate {{RollingRand

[jira] [Created] (LOG4J2-1704) Add a Builder to RollingRandomAccessFileAppender and deprecate RollingRandomAccessFileAppender.createAppender()

Gary Gregory created LOG4J2-1704: Summary: Add a Builder to RollingRandomAccessFileAppender and deprecate RollingRandomAccessFileAppender.createAppender() Key: LOG4J2-1704 URL: https://issues.apache.org/jira/brows

[jira] [Reopened] (LOG4J2-1702) Logging file level affecting console level

[ https://issues.apache.org/jira/browse/LOG4J2-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1702: -- > Logging file level affecting console level > -- > >

[jira] [Closed] (LOG4J2-1703) Add a Builder to MemoryMappedFileAppender and deprecate MemoryMappedFileAppender.createAppender()

[ https://issues.apache.org/jira/browse/LOG4J2-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1703. Resolution: Fixed In Git master. > Add a Builder to MemoryMappedFileAppender and deprecate > Memo

[jira] [Issue Comment Deleted] (LOG4J2-1702) Logging file level affecting console level

[ https://issues.apache.org/jira/browse/LOG4J2-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1702: - Comment: was deleted (was: In Git master.) > Logging file level affecting console level > --

[jira] [Closed] (LOG4J2-1702) Logging file level affecting console level

[ https://issues.apache.org/jira/browse/LOG4J2-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1702. Resolution: Fixed In Git master. > Logging file level affecting console level > --

[jira] [Comment Edited] (LOG4J2-1688) Multiple loggings of arguments are setting these arguments to null

[ https://issues.apache.org/jira/browse/LOG4J2-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659329#comment-15659329 ] Remko Popma edited comment on LOG4J2-1688 at 11/12/16 10:16 AM: ---

[jira] [Created] (LOG4J2-1703) Add a Builder to MemoryMappedFileAppender and deprecate MemoryMappedFileAppender.createAppender()

Gary Gregory created LOG4J2-1703: Summary: Add a Builder to MemoryMappedFileAppender and deprecate MemoryMappedFileAppender.createAppender() Key: LOG4J2-1703 URL: https://issues.apache.org/jira/browse/LOG4J2-1703

[jira] [Updated] (LOG4J2-1702) Logging file level affecting console level

[ https://issues.apache.org/jira/browse/LOG4J2-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Senkyr updated LOG4J2-1702: - Description: Please see this question: http://stackoverflow.com/questions/40556645/log4j2-loggin

[jira] [Created] (LOG4J2-1702) Logging file level affecting console level

David Senkyr created LOG4J2-1702: Summary: Logging file level affecting console level Key: LOG4J2-1702 URL: https://issues.apache.org/jira/browse/LOG4J2-1702 Project: Log4j 2 Issue Type: Bug

[deprecation] getContextMap() in LogEvent has been deprecated

Is there search and replace to fix all of these? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition

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

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

[jira] [Closed] (LOG4J2-1701) Add a Builder to RandomAccessFileAppender and deprecate RandomAccessFileAppender.createAppender()

[ https://issues.apache.org/jira/browse/LOG4J2-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1701. Resolution: Fixed In Git master. > Add a Builder to RandomAccessFileAppender and deprecate > Rand

[jira] [Created] (LOG4J2-1701) Add a Builder to RandomAccessFileAppender and deprecate RandomAccessFileAppender.createAppender()

Gary Gregory created LOG4J2-1701: Summary: Add a Builder to RandomAccessFileAppender and deprecate RandomAccessFileAppender.createAppender() Key: LOG4J2-1701 URL: https://issues.apache.org/jira/browse/LOG4J2-1701

[jira] [Commented] (LOG4J2-1688) Multiple loggings of arguments are setting these arguments to null

[ https://issues.apache.org/jira/browse/LOG4J2-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659329#comment-15659329 ] Remko Popma commented on LOG4J2-1688: - The test needs to wait for the background thre

Jenkins build became unstable: Log4j 2.x #2460

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

Re: builds@a.o is so sloooooooow

It is a code coverage web site, for example https://coveralls.io/github/garydgregory/jcommander-addons?branch=master Gary On Sat, Nov 12, 2016 at 12:09 AM, Ralph Goers wrote: > What is/are coveralls? Well, I used to own a pair but I don’t think that > is what you mean. > > Ralph > > On Nov 11,

Re: builds@a.o is so sloooooooow

What is/are coveralls? Well, I used to own a pair but I don’t think that is what you mean. Ralph > On Nov 11, 2016, at 8:29 PM, Gary Gregory wrote: > > Also Coveralls: https://issues.apache.org/jira/browse/INFRA-12901 > > > Gary > > On Fr

category = "Core"

I notice that we have Plugins that are NOT in log4j-core that use category = "Core". Is that a hack or should these be changed to category = "WhateverModuleILiveIn"? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition