OK - I have verified that FileAppenderPermissionsTest is flawed on OS X. It is
reading /etc/groups to find a group for the user. If it doesn’t find a group
then it tries to use the user’s name - which doesn’t work because there is no
group with that name. On MacOS /etc/groups is only used in sin
Reopen the issue. Once the issue is closed, you can only add comments, not edit
them.
(Shameless plug) Every java main() method deserves http://picocli.info
> On Jul 15, 2017, at 4:31, Gary Gregory wrote:
>
> Hi All,
>
> What do we have to do to allow us to EDIT comments?
>
> Gary
> Typo Ma
[
https://issues.apache.org/jira/browse/LOG4J2-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088182#comment-16088182
]
Gary Gregory commented on LOG4J2-1421:
--
Hi All,
But that does not solve the initial
Let fix my description:
I have a case where I pass -D*log4j.debug=false* to the JVM AND my config
says *status="trace"* and Status logger info() calls are NOT logged to the
console but debug() and trace() events ARE.
Gary
On Fri, Jul 14, 2017 at 2:34 PM, Gary Gregory
wrote:
> Hi All:
>
> I hav
[
https://issues.apache.org/jira/browse/LOG4J2-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088126#comment-16088126
]
Gary Gregory commented on LOG4J2-1421:
--
Note that filters should be annotated with:
Hi All:
I have a case where I pass -Dlog4j.debug=true to the JVM AND my config says
status="TRACE" and Status logger info() calls are NOT logged to the console.
Seen that?
Gary
On Fri, Jul 14, 2017 at 1:49 PM, Matt Sicker wrote:
> The old names are all translated to normalized names via some magical
> regular expressions from what I recall. I should have some time to work on
> Log4j stuff this weekend, so I'll try to get that merged as well.
>
Thank you sir.
Gary
>
On Fri, Jul 14, 2017 at 1:48 PM, Matt Sicker wrote:
> Said branch continues to support the alternate naming schemes as fallbacks,
> but it prioritizes the log4j2.* naming scheme.
>
Please. Please. Please. I do not need to track this kind of noise :-P
G
> On 14 July 2017 at 15:47, Matt Sicker
The old names are all translated to normalized names via some magical
regular expressions from what I recall. I should have some time to work on
Log4j stuff this weekend, so I'll try to get that merged as well.
On 14 July 2017 at 15:48, Gary Gregory wrote:
> Merge it! :-)
>
> Did you bother to k
Merge it! :-)
Did you bother to keep the old names for compat?
G
On Fri, Jul 14, 2017 at 1:47 PM, Matt Sicker wrote:
> I have an open branch that fixes all this. The only remaining work there is
> to clean up merge conflicts and update the documentation to use log4j2.*
> everywhere.
>
> On 14
Said branch continues to support the alternate naming schemes as fallbacks,
but it prioritizes the log4j2.* naming scheme.
On 14 July 2017 at 15:47, Matt Sicker wrote:
> I have an open branch that fixes all this. The only remaining work there
> is to clean up merge conflicts and update the docum
I have an open branch that fixes all this. The only remaining work there is
to clean up merge conflicts and update the documentation to use log4j2.*
everywhere.
On 14 July 2017 at 15:46, Gary Gregory wrote:
> Hi All,
>
> Our sys prop naming is driving me nuts!
>
> Sometimes it's "log4j.foo", som
Hi All,
Our sys prop naming is driving me nuts!
Sometimes it's "log4j.foo", sometimes it's "log4j*2*.bar", sometimes its
"bar". WTF!
Can we just PLEASE bite the bullet and make it all "log4j2." or _something_
We could keep the existing names for compat (TDB).
?
Gary
[
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088012#comment-16088012
]
ASF subversion and git services commented on LOG4J2-1813:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088013#comment-16088013
]
Gary Gregory commented on LOG4J2-1813:
--
Done.
> Provide shorter and more intuitive
It doesn’t sound right to me that they are only loaded once per ClassLoader.
That said, I’m not sure how a plugin could be unloaded.
Ralph
> On Jul 14, 2017, at 12:32 PM, Gary Gregory wrote:
>
> That is fine by me...
>
> Based on https://issues.apache.org/jira/browse/LOG4J2-1421 is seems that
That is fine by me...
Based on https://issues.apache.org/jira/browse/LOG4J2-1421 is seems that
our metadata tooling might be too onerous for some folks, hence the
packages option...
Gary
On Fri, Jul 14, 2017 at 12:16 PM, Matt Sicker wrote:
> Maybe packages shouldn't be a configuration file opt
Hi All,
What do we have to do to allow us to EDIT comments?
Gary
Typo Master Level 2.
[
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087856#comment-16087856
]
Gary Gregory commented on LOG4J2-1813:
--
Which is:
- {{-Dlog4j2.debug}} means DEBUG i
Maybe packages shouldn't be a configuration file option considering the
limitations?
On 14 July 2017 at 13:58, Gary Gregory wrote:
> Hi All:
>
> We document "packages" as:
>
> A comma separated list of package names to search for plugins. Plugins are
> only loaded once per classloader so changin
[
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087829#comment-16087829
]
ASF subversion and git services commented on LOG4J2-1813:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087826#comment-16087826
]
Gary Gregory commented on LOG4J2-1813:
--
I plan on change this implementation such th
Hi All:
We document "packages" as:
A comma separated list of package names to search for plugins. Plugins are
only loaded once per classloader so changing this value may not have any
effect upon reconfiguration.
That seems quite restrictive:
- Start app without "packages" in Log4j config
- Reco
I know we've kinda covered this topic before to some extent back before
ApacheCon. I'm planning to do a general logging presentation this November
at my local Java user group (thanks for the idea, Gary!), and I was
wondering if any of you had any useful source material or tips about what
to cover.
Yes. I did that to the rolling tests but I don't know whether the tests are bad
for the permission stuff or whether the functionality doesn't work on MacOS, in
which case it would need to be disabled.
Ralph
> On Jul 14, 2017, at 8:01 AM, Gary Gregory wrote:
>
> I assume you will be adding JUn
[
https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087439#comment-16087439
]
Matt Sicker commented on LOG4J2-1979:
-
Which would be here: https://issues.apache.org
[
https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087438#comment-16087438
]
Gary Gregory commented on LOG4J2-1979:
--
Right, so you might want to start in Commons
I assume you will be adding JUnit Assume calls to skip these tests?
Gary
On Jul 14, 2017 00:01, "Ralph Goers" wrote:
> After ignoring the test causing the previous problem I am now encountering
> errors with the new permissions test. I am disabling the
> RollingAppenderDirect test since it also
[
https://issues.apache.org/jira/browse/LOG4J2-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087253#comment-16087253
]
Ralph Goers commented on LOG4J2-1979:
-
A downside to this is that this class derives
João Paulo Lemes Machado created LOG4J2-1979:
Summary: Refactoring of StrSubstitutor
Key: LOG4J2-1979
URL: https://issues.apache.org/jira/browse/LOG4J2-1979
Project: Log4j 2
Issue
[
https://issues.apache.org/jira/browse/LOG4J2-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086785#comment-16086785
]
Paul Burrowes edited comment on LOG4J2-1421 at 7/14/17 9:16 AM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086785#comment-16086785
]
Paul Burrowes edited comment on LOG4J2-1421 at 7/14/17 9:16 AM:
---
After ignoring the test causing the previous problem I am now encountering
errors with the new permissions test. I am disabling the RollingAppenderDirect
test since it also will have the same problem with FileWatcher, but I don’t
know the cause of the other failures.
Ralph
ERROR] Failures:
[E
33 matches
Mail list logo
