Re: @PluginElement for Maps?

On Fri, Sep 16, 2016 at 8:39 PM, Ralph Goers wrote: > Does my answer to your other email make this question moot? > Kind of but not really :-) We can pause this thread and continue the more meaty discussion in the other thread. Thank you, Gary > > Ralph > > On Sep 16, 2016, at 11:55 AM, Gary G

Re: OS-based dynamic configuration file

On Fri, Sep 16, 2016 at 8:38 PM, Ralph Goers wrote: > Gary, > > I have no problem with components that can be dumbed down to do simple > things. I do have a problem with components that only do simple things > because people will constantly asked to have them be enhanced. > > As for what you are

Re: @PluginElement for Maps?

Does my answer to your other email make this question moot? Ralph > On Sep 16, 2016, at 11:55 AM, Gary Gregory wrote: > > Right now, we can say: > > @PluginFactory > public static ConcurrentMap createAppenders( > @PluginElement("Appenders") final Appender[] appenders) {

Re: OS-based dynamic configuration file

Gary, I have no problem with components that can be dumbed down to do simple things. I do have a problem with components that only do simple things because people will constantly asked to have them be enhanced. As for what you are proposing here, can I just say “No”? Having the Appenders elem

[jira] [Closed] (LOG4J2-1586) Automatic Reconfiguration not working when edit and save log4j2.xml in NetBeans /build/WEB-INF

[ https://issues.apache.org/jira/browse/LOG4J2-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darren Kelly closed LOG4J2-1586. Resolution: Cannot Reproduce > Automatic Reconfiguration not working when edit and save log4j2.xml

[jira] [Commented] (LOG4J2-1586) Automatic Reconfiguration not working when edit and save log4j2.xml in NetBeans /build/WEB-INF

[ https://issues.apache.org/jira/browse/LOG4J2-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15498077#comment-15498077 ] Darren Kelly commented on LOG4J2-1586: -- [[email protected]] My apologies for any inc

[jira] [Commented] (LOG4J2-969) Refactor SyslogAppender so that Layout is a Plugin element

[ https://issues.apache.org/jira/browse/LOG4J2-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497640#comment-15497640 ] James Park commented on LOG4J2-969: --- In reference to the BSD format (RFC3164) mentioned

Re: @PluginElement for Maps?

See AbstractConfiguration.createPluginObject() along with createPluginMap(). On 16 September 2016 at 15:11, Matt Sicker wrote: > There's some sort of support already for Map and Collection as a > @PluginElement, though I've never actually used it. > > On 16 September 2016 at 13:55, Gary Gregory

Re: @PluginElement for Maps?

There's some sort of support already for Map and Collection as a @PluginElement, though I've never actually used it. On 16 September 2016 at 13:55, Gary Gregory wrote: > Right now, we can say: > > @PluginFactory > public static ConcurrentMap createAppenders( > @PluginElem

@PluginElement for Maps?

Right now, we can say: @PluginFactory public static ConcurrentMap createAppenders( @PluginElement("Appenders") final Appender[] appenders) { and you get an array of type Foo, which is really neat. What it be out of bounds to think of doing: @PluginElement("Thing") final

Re: OS-based dynamic configuration file

Now I've dived into this part of the code and consider what this configuration means for my use case, I see that it works and that the new feature has merit on its own but... It feels to me like my specific use case is an edge case of this new routing appender feature: I will only ever have one rou

[jira] [Updated] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1583: Fix Version/s: 2.7 > Nested logging call disrupts output of outer logging call > --

Jenkins build is still unstable: Log4j 2.x #2325

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Assigned] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1583: --- Assignee: Remko Popma > Nested logging call disrupts output of outer logging call >

Re: logging-log4j2 git commit: Document how to access snapshot dependencies

See my next commit. On Fri, Sep 16, 2016 at 6:45 PM, Gary Gregory wrote: > Is the plan to update this text with each release or just leave it at " > 2.6.3-SNAPSHOT"? > > Gary > > -- Forwarded message -- > From: > Date: Fri, Sep 16, 2016 at 4:24 AM > Subject: logging-log4j2 git c

Fwd: logging-log4j2 git commit: Document how to access snapshot dependencies

Is the plan to update this text with each release or just leave it at " 2.6.3-SNAPSHOT"? Gary -- Forwarded message -- From: Date: Fri, Sep 16, 2016 at 4:24 AM Subject: logging-log4j2 git commit: Document how to access snapshot dependencies To: [email protected] Reposit

Re: Roadmap for 3.0

The new stop(long,TimeUnit) method on the LifeCycle interface (super interface for Appender, Configuration, Filter and a few more) concerns me. We should introduce a LifeCycle2 extends LifeCycle interface for that method. There may be a few more items. Full list is at https://issues.apache.org

Re: Roadmap for 3.0

That is a very good point! Sent from my iPhone > On Sep 16, 2016, at 8:06 AM, Greg Thomas wrote: > > > Remember that many users haven't migrated from 1.2 yet. > > This. IMHO it will become much harder to persuade people to make a jump to > 2.x if there a 3.x in the pipeline that will break BC

Re: Roadmap for 3.0

I am on the road right now but should have time on Monday to do the 2.7 release. Sent from my iPhone > On Sep 16, 2016, at 7:45 AM, Mikael Ståldal wrote: > > I don't think we should start working on 3.0 any time soon, unless we have to > in order to support Java 9. > > And I think we should m

Re: Roadmap for 3.0

> Remember that many users haven't migrated from 1.2 yet. This. IMHO it will become much harder to persuade people to make a jump to 2.x if there a 3.x in the pipeline that will break BC - they'll just way for 3.x Greg On 16 September 2016 at 15:45, Mikael Ståldal wrote: > I don't think we sho

Re: Roadmap for 3.0

I don't think we should start working on 3.0 any time soon, unless we have to in order to support Java 9. And I think we should make a 2.7 release really soon, and then more 2.x releases after that. Remember that many users haven't migrated from 1.2 yet. On Thu, Sep 15, 2016 at 8:36 PM, Gary Gre

Re: Document where to find snapshot builds

We have a variable for the current release version. The site plugin runs against the release tag so I don't see how it could know about the next snapshot version. Sent from my iPad > On Sep 16, 2016, at 5:39 AM, Mikael Ståldal wrote: > > Right. > >> On Fri, Sep 16, 2016 at 2:08 PM, Remko Pop

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496415#comment-15496415 ] Ralph Goers commented on LOG4J2-1585: - If I understand what you are doing correctly y

[jira] [Updated] (LOG4J2-1589) Value nesting during property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Neretin updated LOG4J2-1589: Description: There is already a good description what "default value nesting" is: http://l

[jira] [Updated] (LOG4J2-1589) Value nesting during property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Neretin updated LOG4J2-1589: Description: There is already a good description what "default value nesting" is: http://l

[jira] [Updated] (LOG4J2-1589) Value nesting during property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Neretin updated LOG4J2-1589: Description: There is already a good description what "default value nesting" is: http://l

[jira] [Updated] (LOG4J2-1589) Value nesting during property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Neretin updated LOG4J2-1589: Description: There is already a good description what "default value nesting" is: http://l

[jira] [Updated] (LOG4J2-1589) Value nesting during property substitution

[ https://issues.apache.org/jira/browse/LOG4J2-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Neretin updated LOG4J2-1589: Description: There is already a good description what "default value nesting" is: http://l

[jira] [Created] (LOG4J2-1589) Value nesting during property substitution

Dmitriy Neretin created LOG4J2-1589: --- Summary: Value nesting during property substitution Key: LOG4J2-1589 URL: https://issues.apache.org/jira/browse/LOG4J2-1589 Project: Log4j 2 Issue Type

Jenkins build became unstable: Log4j 2.x #2324

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Commented] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496377#comment-15496377 ] Remko Popma commented on LOG4J2-1583: - NOTES TO SELF. PLEASE IGNORE. WILL DELETE SOON

[jira] [Updated] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rainer Schnitker updated LOG4J2-1588: - Description: Log4j2 2.6.x seems to cache the thread name. A revert to version 2.4.1. work

[jira] [Updated] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rainer Schnitker updated LOG4J2-1588: - Description: Log4j2 2.6.x seems to cache the thread name. A revert to version 2.4.1. work

[jira] [Created] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

Rainer Schnitker created LOG4J2-1588: Summary: Console or File Logger caches thread name, but not in older log4j2 versions Key: LOG4J2-1588 URL: https://issues.apache.org/jira/browse/LOG4J2-1588 P

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

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: Document where to find snapshot builds

Right. On Fri, Sep 16, 2016 at 2:08 PM, Remko Popma wrote: > I don't think we have such a variable. At the time of any release we > usually don't know whether the next release will be a minor or a patch > release. > > Maybe better to use a generic description rather than a version number? > > Se

[jira] [Commented] (LOG4J2-1583) Nested logging call disrupts output of outer logging call

[ https://issues.apache.org/jira/browse/LOG4J2-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496229#comment-15496229 ] Remko Popma commented on LOG4J2-1583: - I see the problem. Basically in the current co

Re: Document where to find snapshot builds

I don't think we have such a variable. At the time of any release we usually don't know whether the next release will be a minor or a patch release. Maybe better to use a generic description rather than a version number? Sent from my iPhone > On 2016/09/16, at 20:25, Mikael Ståldal wrote: >

[jira] [Updated] (LOG4J2-1576) Better automated backwards compatibility checking

[ https://issues.apache.org/jira/browse/LOG4J2-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1576: Description: I have trouble running Clirr on a machine that only has Java 8 (ran into the "Invalid

Re: Document where to find snapshot builds

OK, added it. Is there any template variable to use instead of putting "2.6.3-SNAPSHOT" into the maven-artifacts.xml.vm? On Thu, Sep 15, 2016 at 5:50 PM, Remko Popma wrote: > If you want to document this, go for it! > > Sent from my iPhone > > On 2016/09/16, at 0:35, Gary Gregory wrote: > > +1

[jira] [Commented] (LOG4J2-1587) Build process should work on Java 8

[ https://issues.apache.org/jira/browse/LOG4J2-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496062#comment-15496062 ] Remko Popma commented on LOG4J2-1587: - LOG4J2-1576 is looking at Clirr alternatives.

[jira] [Commented] (LOG4J2-1010) Injectable context properties

[ https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496055#comment-15496055 ] Remko Popma commented on LOG4J2-1010: - Mikael, now I see what you mean. Yes, I agree

[jira] [Commented] (LOG4J2-1586) Automatic Reconfiguration not working when edit and save log4j2.xml in NetBeans /build/WEB-INF

[ https://issues.apache.org/jira/browse/LOG4J2-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496047#comment-15496047 ] Remko Popma commented on LOG4J2-1586: - Isn't the /build/web/WEB-INF/classes/ directo

[jira] [Commented] (LOG4J2-1585) Logger.getParent gives warning about MessageFactory mismatch

[ https://issues.apache.org/jira/browse/LOG4J2-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496027#comment-15496027 ] Remko Popma commented on LOG4J2-1585: - I looked at this in more detail. I can see [~s