[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-1766.
--
Resolution: Fixed
Fix Version/s: 2.9
Partial patch applied followed up by a few tweaks.
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064368#comment-16064368
]
ASF subversion and git services commented on LOG4J2-1766:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Component/s: Code
> unable to install log4php via pear: unable to resolv hostname pea
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Environment: centos 7, php 5.6 via rh scl repo and php 5.6, 7.0 and 7.1
with webtatic
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Priority: Critical (was: Major)
> unable to install log4php via pear: unable to reso
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Description:
When trying the discover part of pear for the pear.apache.org/log4php vi
Dietrich Streifert created LOG4PHP-237:
--
Summary: unable to install log4php via pear: unable to resolv
hostname pear.apache.org
Key: LOG4PHP-237
URL: https://issues.apache.org/jira/browse/LOG4PHP-237
[
https://issues.apache.org/jira/browse/LOG4J2-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064339#comment-16064339
]
Gary Gregory commented on LOG4J2-1949:
--
Thank you for your report.
Do you feel like
[
https://issues.apache.org/jira/browse/LOG4J2-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064336#comment-16064336
]
Gary Gregory commented on LOG4J2-1958:
--
Should we log a status logger warning if a {
Mikael Ståldal created LOG4J2-1958:
--
Summary: Deprecate SerializedLayout and remove it as default
Key: LOG4J2-1958
URL: https://issues.apache.org/jira/browse/LOG4J2-1958
Project: Log4j 2
Iss
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063649#comment-16063649
]
Pierrick HYMBERT commented on LOG4J2-1950:
--
Just build from default windows dock
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063619#comment-16063619
]
Gary Gregory commented on LOG4J2-1950:
--
What is the command you use?
> Docker build
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063617#comment-16063617
]
Pierrick HYMBERT commented on LOG4J2-1950:
--
Yes Windows docker machine just work
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063609#comment-16063609
]
Gary Gregory commented on LOG4J2-1950:
--
Can I run this on the Windows 10 command lin
... oups sorry, just need to be patient :-)
Please review when you have time
Le lun. 26 juin 2017 à 21:20, Pierrick HYMBERT
a écrit :
> Hello,
>
> I face a strange behavior on github PR #88, I integrated feedback from
> Gary, then pushed, my remote branch is updated yet the PR.
> Any idea ?
>
>
Hello,
I face a strange behavior on github PR #88, I integrated feedback from
Gary, then pushed, my remote branch is updated yet the PR.
Any idea ?
PR shows only 1 original PR commit:
https://github.com/apache/logging-log4j2/pull/88
Related ahead forked branch has 4 commits:
https://github.com/p
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063536#comment-16063536
]
Pierrick HYMBERT commented on LOG4J2-1950:
--
BTW, Log4j 1.x Compatibility API fai
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierrick HYMBERT closed LOG4J2-1950.
OK, building. Thanks
> Docker build broken with log4j-api-java9
>
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063326#comment-16063326
]
ASF GitHub Bot commented on LOG4J2-1766:
Github user garydgregory commented on a
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063325#comment-16063325
]
ASF GitHub Bot commented on LOG4J2-1766:
Github user garydgregory commented on a
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063324#comment-16063324
]
ASF GitHub Bot commented on LOG4J2-1766:
Github user garydgregory commented on a
Github user garydgregory commented on a diff in the pull request:
https://github.com/apache/logging-log4j2/pull/88#discussion_r124051332
--- Diff:
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/DefaultRolloverStrategy.java
---
@@ -83,6 +85,195 @@
Github user garydgregory commented on a diff in the pull request:
https://github.com/apache/logging-log4j2/pull/88#discussion_r124051928
--- Diff:
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/DefaultRolloverStrategy.java
---
@@ -94,8 +285,10 @@
Github user garydgregory commented on a diff in the pull request:
https://github.com/apache/logging-log4j2/pull/88#discussion_r124051596
--- Diff:
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/rolling/DefaultRolloverStrategy.java
---
@@ -83,6 +85,195 @@
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1766:
-
Description:
I have the following log configuration.
{code:xml}
%d{yyy
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-1950.
--
Resolution: Fixed
Fix Version/s: 2.9
In git master. Please verify and close.
> Docker b
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063292#comment-16063292
]
ASF GitHub Bot commented on LOG4J2-1950:
Github user asfgit closed the pull reque
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/84
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
[
https://issues.apache.org/jira/browse/LOG4J2-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063290#comment-16063290
]
ASF subversion and git services commented on LOG4J2-1950:
-
Commit
Could be. That falls into the better safe than sorry category. If some
plugin uses a char[] because it wants to/need to and it is not a sensitive
item, then it's not that big of a deal to say 'sensitve = true' if you
realize you do want that. I am not sure how often anyone would use a char[]
for an
This makes me think that char[] fields/params should have the
sensitive=true set by default.
On 25 June 2017 at 21:31, wrote:
> Repository: logging-log4j2
> Updated Branches:
> refs/heads/master 07248cdbb -> bcd60cc6d
>
>
> [LOG4J2-1956] JMS Appender broker password should be a char[], not a
>
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063200#comment-16063200
]
ASF GitHub Bot commented on LOG4J2-1766:
Github user jvz commented on the issue:
Github user jvz commented on the issue:
https://github.com/apache/logging-log4j2/pull/86
Depends if the constructors are private or not. For public ones where
having a default value for the new constructor doesn't make much sense,
deprecation is the way to go. When a sensible default
[
https://issues.apache.org/jira/browse/LOG4J2-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063190#comment-16063190
]
Matt Sicker commented on LOG4J2-1957:
-
A possible suggestion on this could be impleme
Mauro Molinari created LOG4J2-1957:
--
Summary: WriterAppender: clarify its usage
Key: LOG4J2-1957
URL: https://issues.apache.org/jira/browse/LOG4J2-1957
Project: Log4j 2
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062637#comment-16062637
]
ASF GitHub Bot commented on LOG4J2-1766:
GitHub user phymbert opened a pull reque
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062638#comment-16062638
]
Pierrick HYMBERT commented on LOG4J2-1766:
--
Please consider this new new PR, I m
GitHub user phymbert opened a pull request:
https://github.com/apache/logging-log4j2/pull/88
[LOG4J2-1766] Temporary compress directory during rollover
commit a135e42cbafcaee88a015af80e4f411d688934e5
Merge: 5fe81f4 d66b640
Author: phymbert
Date: Mon Jun 26 10:48:52 201
[
https://issues.apache.org/jira/browse/LOG4J2-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062635#comment-16062635
]
ASF GitHub Bot commented on LOG4J2-1766:
Github user phymbert closed the pull req
Github user phymbert closed the pull request at:
https://github.com/apache/logging-log4j2/pull/86
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featur
I did not realize the sites were archived. That's great. We only need to
document that fact and link.
Gary
On Jun 25, 2017 21:57, "Ralph Goers" wrote:
The Legacy section on the left nav bar contains a link for Log4j 1.x and
Log4j 2.3. These two releases (and sites) have special significance. No
41 matches
Mail list logo
