Re: Builder pattern

2016-11-14 Thread Matt Sicker
I'd support deprecating the with methods and making set methods the canonical one. As for is versus get, is it because some of them return Boolean rather than boolean? I generally prefer the is prefix for boolean and avoid using Boolean whenever possible. On 14 November 2016 at 17:37, Gary Gregor

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

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665526#comment-15665526 ] Gary Gregory commented on LOG4J2-1705: -- The new Git repo is here: https://git-wip-u

[jira] [Issue Comment Deleted] (LOG4J2-1705) Kotlin wrapper for Log4j 2 API

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1705: - Comment: was deleted (was: I asked INFRA for a new repo with [INFRA-12861].) > Kotlin wrapper fo

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

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1705: - Affects Version/s: (was: 2.6.2) (was: 2.7) > Kotlin wrapper for Lo

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

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665420#comment-15665420 ] Gary Gregory commented on LOG4J2-1705: -- I asked INFRA for a new repo with [INFRA-128

Re: Builder pattern

2016-11-14 Thread Gary Gregory
I marked existing methods @Deprecated. I did not delete anything in order to avoid breaking BC as much as possible. I'd like to change the existing Builders that use "with" to "set". This would not break config files but it would break code. Is it over the top to deprecate the "with" methods and a

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

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1709. Resolution: Fixed Assignee: Gary Gregory Fix Version/s: 2.8 In Git master. > Add a

Re: Builder pattern

2016-11-14 Thread Remko Popma
Of course only for the Builders that were published as of 2.7. The Builders we're adding in 2.8 can just use set. Sent from my iPhone > On 15 Nov 2016, at 8:26, Remko Popma wrote: > > Are Builders used by users for custom plugins? > Should we deprecate and keep the old methods around for a wh

Re: Builder pattern

2016-11-14 Thread Remko Popma
Are Builders used by users for custom plugins? Should we deprecate and keep the old methods around for a while to avoid breaking user code? Remko Sent from my iPhone > On 15 Nov 2016, at 5:22, Matt Sicker wrote: > > I like using set instead of with for builders. I've only been using with > m

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

2016-11-14 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-1709: Summary: Add a Builder to SyslogAppender and deprecate SyslogAppender.createAppender(). Key: LOG4J2-1709 URL: https://issues.apache.org/jira/browse/LOG4J2-1709 Projec

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

2016-11-14 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665115#comment-15665115 ] Ralph Goers commented on LOG4J2-1686: - XSL to do what? Generate the configuration? Th

Jenkins build became unstable: Log4j 2.x #2482

2016-11-14 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Re: Builder pattern

2016-11-14 Thread Matt Sicker
I like using set instead of with for builders. I've only been using with methods lately for constructing modified copies of the current object which doesn't exactly fit the builder idea (since the builder is modified and not copied). I've also used builders without any prefix, but that would look r

Builder pattern

2016-11-14 Thread Gary Gregory
I recently added a bunch of Builders in various places and used "with" as the setter method prefix. We have a mix of "set" and "with" in our Builders ATM. I am thinking of going back and changing the builders I added since 2.7 from "with" to "set". I am liking "set" better because: - More standa

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

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664805#comment-15664805 ] Raman Gupta commented on LOG4J2-1705: - Pending: * tests * location-aware logging >

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

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664796#comment-15664796 ] Raman Gupta commented on LOG4J2-1705: - Thanks, removed! > Kotlin wrapper for Log4j 2

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

2016-11-14 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664775#comment-15664775 ] Matt Sicker commented on LOG4J2-1705: - It doesn't look like you actually need log4j-c

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

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664726#comment-15664726 ] Raman Gupta commented on LOG4J2-1705: - Work in progress @ https://github.com/rocketra

[jira] [Commented] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664647#comment-15664647 ] Gary Gregory commented on LOG4J2-1686: -- For completeness and complication I feel lik

Re: [1/4] logging-log4j2 git commit: LOG4J2-1692: Add putAll() / pushAll() methods to CloseableThreadContext

2016-11-14 Thread Gary Gregory
OK, cool! :-) Gary On Mon, Nov 14, 2016 at 10:30 AM, Greg Thomas wrote: > Already fixed in trunk @ https://github.com/apache/ > logging-log4j2/blob/master/log4j-api/src/main/java/org/ > apache/logging/log4j/CloseableThreadContext.java > > I think the merge of my pull request copied all the commi

Re: [1/4] logging-log4j2 git commit: LOG4J2-1692: Add putAll() / pushAll() methods to CloseableThreadContext

2016-11-14 Thread Greg Thomas
Already fixed in trunk @ https://github.com/apache/logging-log4j2/blob/master/log4j-api/src/main/java/org/apache/logging/log4j/CloseableThreadContext.java I think the merge of my pull request copied all the commits, you weren't the only one to spot that! Greg -- Sent from my iPhone > On 14

Fwd: [1/4] logging-log4j2 git commit: LOG4J2-1692: Add putAll() / pushAll() methods to CloseableThreadContext

2016-11-14 Thread Gary Gregory
Note that "@since 2.7.1" should all be "@since 2.8" Gary -- Forwarded message -- From: Date: Mon, Nov 14, 2016 at 2:17 AM Subject: [1/4] logging-log4j2 git commit: LOG4J2-1692: Add putAll() / pushAll() methods to CloseableThreadContext To: comm...@logging.apache.org Repository:

[jira] [Comment Edited] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664505#comment-15664505 ] Ralph Goers edited comment on LOG4J2-1686 at 11/14/16 5:42 PM:

[jira] [Commented] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664505#comment-15664505 ] Ralph Goers commented on LOG4J2-1686: - Thanks for looking. You are correct that the d

[jira] [Comment Edited] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664359#comment-15664359 ] Raman Gupta edited comment on LOG4J2-1686 at 11/14/16 4:35 PM:

[jira] [Comment Edited] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664359#comment-15664359 ] Raman Gupta edited comment on LOG4J2-1686 at 11/14/16 4:33 PM:

[jira] [Commented] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664359#comment-15664359 ] Raman Gupta commented on LOG4J2-1686: - I like the idea of `ScriptPropertiesSelector`.

[jira] [Commented] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664341#comment-15664341 ] Mikael Ståldal commented on LOG4J2-1686: Is the documentation example for {{Scrip

Re: Fwd: [1/2] logging-log4j2 git commit: Coveralls support.

2016-11-14 Thread Gary Gregory
Don't thank me yet, it still does not work! :-( On Nov 14, 2016 7:10 AM, "Matt Sicker" wrote: > Thanks for handling this! :) > > -- Forwarded message -- > From: > Date: 13 November 2016 at 18:30 > Subject: [1/2] logging-log4j2 git commit: Coveralls support. > To: comm...@logging

[jira] [Commented] (LOG4J2-1683) (GC) Avoid allocating temporary objects in MapMessage

2016-11-14 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664253#comment-15664253 ] Ralph Goers commented on LOG4J2-1683: - OK. That was mainly what I was after. > (GC)

[jira] [Comment Edited] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664246#comment-15664246 ] Ralph Goers edited comment on LOG4J2-1686 at 11/14/16 3:49 PM:

[jira] [Commented] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Ralph Goers (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664246#comment-15664246 ] Ralph Goers commented on LOG4J2-1686: - Yes, I can some value in that as you might wan

[jira] [Commented] (LOG4J2-1683) (GC) Avoid allocating temporary objects in MapMessage

2016-11-14 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664232#comment-15664232 ] Remko Popma commented on LOG4J2-1683: - I introduced interfaces IndexedStringMap and I

Re: Travis CI

2016-11-14 Thread Matt Sicker
When I used jacoco in a multimodule project before, I had to add a task to combine all the results files into a single one. Though can you set up the plugin to not run on the parent pom? That could be causing an issue. Otherwise, it would probably make sense regardless to aggregate the coverage xm

Fwd: [1/2] logging-log4j2 git commit: Coveralls support.

2016-11-14 Thread Matt Sicker
Thanks for handling this! :) -- Forwarded message -- From: Date: 13 November 2016 at 18:30 Subject: [1/2] logging-log4j2 git commit: Coveralls support. To: comm...@logging.apache.org Repository: logging-log4j2 Updated Branches: refs/heads/master a3e0b3f7e -> 49bd0924f Covera

[jira] [Commented] (LOG4J2-1686) Support conditional configuration

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664120#comment-15664120 ] Raman Gupta commented on LOG4J2-1686: - There are two aspects of this we are now discu

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

2016-11-14 Thread Raman Gupta (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664019#comment-15664019 ] Raman Gupta commented on LOG4J2-1685: - Yup, I saw what you did and incorporated that

JDK 9 & JDK 9 with Project Jigsaw b144 are available on java.net

2016-11-14 Thread Rory O'Donnell
Hi Nick, Early Access b144 (#5709) for JDK 9 with Project Jigsaw is available on java.net, summary of changes are listed here. Early Access b144 f

Jenkins build is back to normal : Log4j 2.x #2478

2016-11-14 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Comment Edited] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663387#comment-15663387 ] Mikael Ståldal edited comment on LOG4J2-1692 at 11/14/16 10:18 AM:

[jira] [Resolved] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1692. Resolution: Fixed Fix Version/s: 2.8 In Git master. > putAll() method for Closeable

[jira] [Commented] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663385#comment-15663385 ] ASF GitHub Bot commented on LOG4J2-1692: Github user asfgit closed the pull reque

[jira] [Commented] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663372#comment-15663372 ] ASF GitHub Bot commented on LOG4J2-1692: Github user mikaelstaldal commented on t

Build failed in Jenkins: Log4j 2.x #2477

2016-11-14 Thread Apache Jenkins Server
See Changes: [ggregory] [LOG4J2-1707] and [LOG4J2-1708]. [ggregory] Add Travis CI and Coverall badges. [ggregory] Minor formatting. -- [...truncated 3641 lines...] at org.junit.runners.Pare

Re: logging-log4j repositories

2016-11-14 Thread Mikael Ståldal
I think it's better to have one repo per language. Some languages may want to use other build tools than Maven (e.g. sbt for Scala). However, the documentation / site buinding is currently a barrier of entry that we should try to mitigate. On Sun, Nov 13, 2016 at 7:29 PM, Gary Gregory wrote: >

Re: Scala repo

2016-11-14 Thread Mikael Ståldal
Yes, when we have the build process (including documentation/site) working for the new repo. On Sun, Nov 13, 2016 at 3:22 AM, Gary Gregory wrote: > Now that we have a populated Scala repo, shall we remove the Scala modules > from the main repo? > > Gary > > -- > E-Mail: garydgreg...@gmail.com |

Re: Log4j RAT check fail in Scala module

2016-11-14 Thread Mikael Ståldal
If I understand the report correctly, it complains about the files log4j-api-scala_2.11/.cache-main and /log4j-api-scala_2.11/.cache-tests Those files are not in Git, they must have been generated on your machine. On Sat, Nov 12, 2016 at 4:49 AM, Gary Gregory wrote: > I am seeing a RAT check fa

[jira] [Commented] (LOG4J2-1694) Allow to easily add fields with fixed values to JSON output

2016-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663287#comment-15663287 ] Mikael Ståldal commented on LOG4J2-1694: [GelfLayout|http://logging.apache.org/lo

[jira] [Commented] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663283#comment-15663283 ] ASF GitHub Bot commented on LOG4J2-1692: Github user GregDThomas commented on a d

[jira] [Commented] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663267#comment-15663267 ] ASF GitHub Bot commented on LOG4J2-1692: Github user mikaelstaldal commented on a

Jenkins build became unstable: Log4j 2.x #2476

2016-11-14 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org

[jira] [Commented] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663236#comment-15663236 ] ASF GitHub Bot commented on LOG4J2-1692: Github user GregDThomas commented on a d

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

2016-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663210#comment-15663210 ] Mikael Ståldal commented on LOG4J2-1685: Yes, I just tried to explain what I did.

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

2016-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663206#comment-15663206 ] Mikael Ståldal commented on LOG4J2-1685: I tried to avoid the BC changes in {{Scr

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

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663205#comment-15663205 ] Gary Gregory commented on LOG4J2-1685: -- Both branches for this issue can be deleted

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

2016-11-14 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663195#comment-15663195 ] Mikael Ståldal commented on LOG4J2-1685: As far as I can see, the LOG4J2-1685 bra

[jira] [Commented] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663191#comment-15663191 ] ASF GitHub Bot commented on LOG4J2-1692: Github user GregDThomas commented on a d

[jira] [Commented] (LOG4J2-1692) putAll() method for CloseableThreadContext

2016-11-14 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663184#comment-15663184 ] ASF GitHub Bot commented on LOG4J2-1692: Github user GregDThomas commented on a d

[jira] [Updated] (LOG4J2-1708) Allow secure Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1708: - Description: Allow any secure socket Appender to set socket options. At the lowest level, this m

[jira] [Closed] (LOG4J2-1708) Allow secure Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1708. Resolution: Fixed > Allow secure Socket Appender to set socket options > --

[jira] [Updated] (LOG4J2-1707) Allow TCP Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1707: - Description: Allow any TCP {{Socket}} Appender to set socket options. At the lowest level, this

[jira] [Reopened] (LOG4J2-1708) Allow secure Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1708: -- > Allow secure Socket Appender to set socket options >

[jira] [Closed] (LOG4J2-1707) Allow TCP Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1707. Resolution: Fixed > Allow TCP Socket Appender to set socket options > -

[jira] [Reopened] (LOG4J2-1707) Allow TCP Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1707: -- > Allow TCP Socket Appender to set socket options > ---

[jira] [Commented] (LOG4J2-1191) Log4j completely hangs in TcpSocketManager after a while...

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663148#comment-15663148 ] Gary Gregory commented on LOG4J2-1191: -- If you try the latest from Git master you ca

[jira] [Closed] (LOG4J2-1707) Allow TCP Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1707. Resolution: Fixed Fix Version/s: 2.8 > Allow TCP Socket Appender to set socket options > ---

[jira] [Closed] (LOG4J2-1708) Allow secure Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1708. Resolution: Fixed Fix Version/s: 2.8 In Git master. > Allow secure Socket Appender to set s

[jira] [Closed] (LOG4J2-1707) Allow TCP Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1707. Resolution: Fixed In Git master. > Allow TCP Socket Appender to set socket options > -

[jira] [Reopened] (LOG4J2-1707) Allow TCP Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1707: -- > Allow TCP Socket Appender to set socket options > ---

Travis CI

2016-11-14 Thread Gary Gregory
We have a Travis CI (https://travis-ci.org/apache/logging-log4j2/) build running but I cannot get the Maven Coveralls Plugin to behave. The build is green (it builds) BUT I always get this at the bottom of the _raw_ log: [ERROR] Failed to execute goal org.eluder.coveralls:coveralls-maven-plugin:4

[jira] [Updated] (LOG4J2-1708) Allow secure Socket Appender to set socket options

2016-11-14 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1708: - Summary: Allow secure Socket Appender to set socket options (was: Allow Secure Socket Appender t