[jira] [Commented] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776042#comment-13776042 ] Frank Steinmann commented on LOG4J2-409: Ralph, you are right with the leading sla

Re: Next release version...

Yeah, but It doesn't really much matter if it is fixed now or not. I can change the release number when the release is performed fairly easily. Ralph On Sep 23, 2013, at 4:34 PM, Gary Gregory wrote: > ...is currently 2.0RC1, should it not be 2.0-RC1, with a dash, like all of > our other previ

Next release version...

...is currently 2.0RC1, should it not be 2.0-RC1, with a dash, like all of our other previous versions? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition

Re: Class name org.apache.logging.log4j.LoggingException

IO (input/output) is a verb (or at least some kind of action). That said, regardless of whether the noun vs verb argument makes any sense I still don't think renaming is necessary. Raph On Sep 23, 2013, at 4:27 PM, Gary Gregory wrote: > Hi Ralph, > > I don't buy the noun vs. verb argument. W

Re: Class name org.apache.logging.log4j.LoggingException

Hi Ralph, I don't buy the noun vs. verb argument. What about IOException and SQLException? By that argument we'd have SQLingExcption and IOingException ;) There are plenty of Exception and Exception. IllegalStateException is another good one, it denotes state, not that you are doing something. Bot

Re: Class name org.apache.logging.log4j.LoggingException

I don't really like "Log4jException". Log4j is a noun while Logging is a verb - it is not meant to imply an exception that applies to all of org.apache.logging but an exception performing logging within Log4j. As such, its current name and package seem quite appropriate to me. Ralph On Sep 23,

[jira] [Commented] (LOG4J2-404) "@EnterpriseNumber" is missing in the ID of structured data when RFC5424Layout is used

[ https://issues.apache.org/jira/browse/LOG4J2-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775774#comment-13775774 ] Ralph Goers commented on LOG4J2-404: This is a side effect of LOG4J2-355 which you app

Re: Class name org.apache.logging.log4j.LoggingException

I don't really like "Log4jException". Log4j is a noun while Logging is a verb - it is not meant to imply an exception that applies to all of org.apache.logging but an exception performing logging within Log4j. As such, its current name and package seem quite appropriate to me. Ralph On Sep 23,

Class name org.apache.logging.log4j.LoggingException

Hi All: I would expected a LoggingException to be in the org.apache.logging package and be used by all org.apache.logging logging solutions, of which there is only one now: Log4j, In org.apache.logging.log4j, I would expect us to have a Log4jException. I propose: (1) renaming org.apache.logging

[jira] [Commented] (LOG4J2-404) "@EnterpriseNumber" is missing in the ID of structured data when RFC5424Layout is used

[ https://issues.apache.org/jira/browse/LOG4J2-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775744#comment-13775744 ] Gary Gregory commented on LOG4J2-404: - Ralph, I think you did some work recently in th

[jira] [Commented] (LOG4J2-378) Logging generates file named ${sys on some systems

[ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775619#comment-13775619 ] Eric Schwarzenbach commented on LOG4J2-378: --- It occurs to me that configuration

[jira] [Commented] (LOG4J2-378) Logging generates file named ${sys on some systems

[ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775609#comment-13775609 ] Eric Schwarzenbach commented on LOG4J2-378: --- It looks like the "myapp.log" file

[jira] [Comment Edited] (LOG4J2-378) Logging generates file named ${sys on some systems

[ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775598#comment-13775598 ] Eric Schwarzenbach edited comment on LOG4J2-378 at 9/23/13 7:49 PM:

[jira] [Comment Edited] (LOG4J2-378) Logging generates file named ${sys on some systems

[ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775598#comment-13775598 ] Eric Schwarzenbach edited comment on LOG4J2-378 at 9/23/13 7:48 PM:

[jira] [Commented] (LOG4J2-378) Logging generates file named ${sys on some systems

[ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775598#comment-13775598 ] Eric Schwarzenbach commented on LOG4J2-378: --- What happens on Ubuntu seems to be

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775582#comment-13775582 ] Tomasz Wladzinski commented on LOG4J2-344: -- I switched addFilter to the one with

[jira] [Commented] (LOG4J2-354) log4j2 + FastFileAppender + Tomcat logrotate problem

[ https://issues.apache.org/jira/browse/LOG4J2-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774751#comment-13774751 ] Kamil Mroczek commented on LOG4J2-354: -- I haven't had time to fully test the solution

[jira] [Commented] (LOG4J2-378) Logging generates file named ${sys on some systems

[ https://issues.apache.org/jira/browse/LOG4J2-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774716#comment-13774716 ] Eric Schwarzenbach commented on LOG4J2-378: --- Thanks, Ralph. I've now tried this

[jira] [Updated] (LOG4J2-404) "@EnterpriseNumber" is missing in the ID of structured data when RFC5424Layout is used

[ https://issues.apache.org/jira/browse/LOG4J2-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamal Bahadur updated LOG4J2-404: - Priority: Blocker (was: Critical) > "@EnterpriseNumber" is missing in the ID of structured d

[jira] [Commented] (LOG4J2-404) "@EnterpriseNumber" is missing in the ID of structured data when RFC5424Layout is used

[ https://issues.apache.org/jira/browse/LOG4J2-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774734#comment-13774734 ] Kamal Bahadur commented on LOG4J2-404: -- Is there anything I can do to get this patch

[jira] [Comment Edited] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774682#comment-13774682 ] Ralph Goers edited comment on LOG4J2-409 at 9/23/13 4:18 PM: -

[jira] [Commented] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774682#comment-13774682 ] Ralph Goers commented on LOG4J2-409: I'm not sure whether or not the backslashes have

[jira] [Comment Edited] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774598#comment-13774598 ] Nick Williams edited comment on LOG4J2-409 at 9/23/13 2:50 PM: -

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774594#comment-13774594 ] Nick Williams commented on LOG4J2-344: -- Thanks for discovering this, Tomasz! I don't

[jira] [Commented] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774598#comment-13774598 ] Nick Williams commented on LOG4J2-409: -- Thanks for reporting this, Frank. Looks like

[jira] [Updated] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

[ https://issues.apache.org/jira/browse/LOG4J2-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Steinmann updated LOG4J2-409: --- Priority: Major (was: Minor) > Specifying log4jConfiguration in web.xml fails on Windows

[jira] [Created] (LOG4J2-409) Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home}

Frank Steinmann created LOG4J2-409: -- Summary: Specifying log4jConfiguration in web.xml fails on Windows when using ${user.home} Key: LOG4J2-409 URL: https://issues.apache.org/jira/browse/LOG4J2-409 P

[jira] [Comment Edited] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774493#comment-13774493 ] Tomasz Wladzinski edited comment on LOG4J2-344 at 9/23/13 12:11 PM:

[jira] [Commented] (LOG4J2-344) Log4j2 doesnt work with Weblogic 12c

[ https://issues.apache.org/jira/browse/LOG4J2-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774493#comment-13774493 ] Tomasz Wladzinski commented on LOG4J2-344: -- I had the same issue. My investigatio