On Sun, May 7, 2017 at 5:28 PM, Gary Gregory wrote:
> On Sun, May 7, 2017 at 4:52 PM, Remko Popma wrote:
>
>> Thinking of LOG4J2-1896, how does Apache HttpCore obtain the keystore
>> password? I wonder what other projects do to avoid putting a plaintext
>> password in the configuration.
>>
>
> Y
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000189#comment-16000189
]
Matt Sicker commented on LOG4J2-1902:
-
You can use log4j-1.2-api for compatibility wi
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000183#comment-16000183
]
prayagupd commented on LOG4J2-1902:
---
[~jvz] I have some dependencies who use log4j 1.*
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000180#comment-16000180
]
prayagupd edited comment on LOG4J2-1902 at 5/8/17 2:03 AM:
---
Yes
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000180#comment-16000180
]
prayagupd edited comment on LOG4J2-1902 at 5/8/17 2:03 AM:
---
Yes
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000180#comment-16000180
]
prayagupd edited comment on LOG4J2-1902 at 5/8/17 2:00 AM:
---
Yes
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000180#comment-16000180
]
prayagupd commented on LOG4J2-1902:
---
Yes the log4j2.json is at `test/resources/log4j2.j
Github user liyuj closed the pull request at:
https://github.com/apache/logging-log4j2/pull/74
---
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 i
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/74
We found a bug that is being corrected and then resubmitted in the form of
a new module.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000153#comment-16000153
]
Remko Popma edited comment on LOG4J2-1902 at 5/8/17 1:06 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000153#comment-16000153
]
Remko Popma commented on LOG4J2-1902:
-
Thanks for checking the classpath.
About the
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000142#comment-16000142
]
Matt Sicker commented on LOG4J2-1902:
-
Unrelated issue you have is packaging log4j 1.
On Sun, May 7, 2017 at 4:52 PM, Remko Popma wrote:
> Thinking of LOG4J2-1896, how does Apache HttpCore obtain the keystore
> password? I wonder what other projects do to avoid putting a plaintext
> password in the configuration.
>
You pass it as a char[] to the API. Remember, HC is a just an API
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000133#comment-16000133
]
prayagupd commented on LOG4J2-1902:
---
[~rem...@yahoo.com] log4j-web will be in WEB-INF/l
Thinking of LOG4J2-1896, how does Apache HttpCore obtain the keystore password?
I wonder what other projects do to avoid putting a plaintext password in the
configuration.
(Shameless plug) Every java main() method deserves http://picocli.info
> On May 8, 2017, at 8:41, Gary Gregory wrote:
>
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000124#comment-16000124
]
Remko Popma commented on LOG4J2-1902:
-
I agree that having the log4j-web module on th
Note: Apache HttpCore let's you do this through a TrustStrategy. But I am
not suggesting we use HC, only that we consider a similar feature for 2.9.
G
Gary
On May 7, 2017 3:06 PM, "Gary Gregory" wrote:
> You have to plug in a custom trust manager into an SSL context. We do not
> allow for tha
Some of our arguments are beginning to sound familiar. :-)
Why don't we look at addressing the slow build problem with a different release
plugin first.
I'd feel much better discussing the pros and cons of project structure changes
when we don't have our back against the wall.
Remko
(Sha
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prayagupd updated LOG4J2-1902:
--
Description:
I'm using log4j2 2.8.2 and with log4j-web, the shutdown hook is supposed to
disabled auto
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prayagupd updated LOG4J2-1902:
--
Description:
I'm using log4j2 2.8.2 and with log4j-web, the shutdown hook is supposed to
disabled auto
[
https://issues.apache.org/jira/browse/LOG4J2-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prayagupd updated LOG4J2-1902:
--
Description:
I'm using log4j2 2.8.2 and with log4j-web, the shutdown hook is supposed to
disabled auto
prayagupd created LOG4J2-1902:
-
Summary: log4j2-web does not disable shutdownHook
Key: LOG4J2-1902
URL: https://issues.apache.org/jira/browse/LOG4J2-1902
Project: Log4j 2
Issue Type: Question
You have to plug in a custom trust manager into an SSL context. We do not
allow for that in our config. We could ship a TM that does that and logs a
"not for production" warning.
Gary
On May 7, 2017 2:26 PM, "Matt Sicker" wrote:
> You can import the self signed certificate into a key store and
You can import the self signed certificate into a key store and configure
that in the socket appender. I'm not sure if the SSL code in Java lets you
just blindly accept all self-signed certificates.
On 6 May 2017 at 23:21, Gary Gregory wrote:
> Hi all,
>
> I do not see a way to configure SSL wit
That all relates to my desire to make a stable SPI for plugins. It allows
the plugins to be released on their own release trains without any worries.
On 7 May 2017 at 15:17, Gary Gregory wrote:
> On May 7, 2017 12:25 PM, "Ralph Goers" wrote:
>
> I understand your point of view, but if we make c
On May 7, 2017 12:25 PM, "Ralph Goers" wrote:
I understand your point of view, but if we make changes that cause
Appenders and Filters to break then we have made huge mistake as it will
impact many of our downstream customers. Also, those are components we have
said will remain backward compatibl
I understand your point of view, but if we make changes that cause Appenders
and Filters to break then we have made huge mistake as it will impact many of
our downstream customers. Also, those are components we have said will remain
backward compatible. Any change that would break these componen
Just re-enabled the "site" target in Jenkins so we can get a snapshot site
available. Also fixed the email address for notifications as it was still
on the old mailing list, so we wouldn't get any notifications.
On 7 May 2017 at 12:43, Gary Gregory wrote:
> Ok, I did that for the "Scala API" and
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated LOG4J2-1901:
--
Description:
The travis-ci build has been failing for weeks e.g.
https://travis-ci.org
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated LOG4J2-1901:
--
Description:
The travis-ci build has been failing for weeks e.g.
https://travis-ci.org
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1581#comment-1581
]
ASF GitHub Bot commented on LOG4J2-1901:
GitHub user PascalSchumacher opened a pu
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/logging-log4j2/pull/77
LOG4J2-1901 - Fix travis-ci build
temporary comment out failing asserts to see if build passes
Just a test, not ready to merge!
You can merge this pull request into a Git re
Hi all,
My 2c and I'll stop: It's not so much that things are stable now, it is
what will happen next.
I've been in situations where mostly internal code (like our core but not
our API) needs to evolve but is forced to do a delicate dance and
negotiation because downstream components would break
I think we should have multiple repos, but I don’t believe we would ever want
them to be fine grained. As I said earlier, The Flume Appender hasn’t changed
much in a couple of years and the changes made to it are more likely to be due
to changes in Flume than in Log4j. I imagine the same could b
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1564#comment-1564
]
ASF GitHub Bot commented on LOG4J2-1901:
Github user asfgit closed the pull reque
[
https://issues.apache.org/jira/browse/LOG4J2-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1565#comment-1565
]
Gary Gregory commented on LOG4J2-1901:
--
I committed PR 76. Thank you Pascal!
> Fix
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/76
---
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
Ok, I did that for the "Scala API" and "Scaladoc" items. Check it out and
see if you like it.
Gary
On Wed, May 3, 2017 at 1:24 AM, Mikael Ståldal
wrote:
> Sounds good.
>
> On Wed, May 3, 2017 at 3:45 AM, Matt Sicker wrote:
>
> > I'd like that idea to give it more visibility as well.
> >
> > On
Pascal Schumacher created LOG4J2-1901:
-
Summary: Fix travis-ci build
Key: LOG4J2-1901
URL: https://issues.apache.org/jira/browse/LOG4J2-1901
Project: Log4j 2
Issue Type: Bug
R
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1555#comment-1555
]
Gary Gregory commented on LOG4J2-1896:
--
Up to you. I was going to leave it as is and
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1548#comment-1548
]
Remko Popma commented on LOG4J2-1896:
-
Cool, thanks!
Do you think it's a good idea to
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1547#comment-1547
]
ASF subversion and git services commented on LOG4J2-1896:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1546#comment-1546
]
ASF subversion and git services commented on LOG4J2-1899:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1542#comment-1542
]
Remko Popma edited comment on LOG4J2-1896 at 5/7/17 4:57 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1544#comment-1544
]
Gary Gregory commented on LOG4J2-1896:
--
OK, I will update {{changes.xml}}.
> Update
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1542#comment-1542
]
Remko Popma commented on LOG4J2-1896:
-
LOG4J2-1898 is about the builder pattern. I am
[
https://issues.apache.org/jira/browse/LOG4J2-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1529#comment-1529
]
ASF GitHub Bot commented on LOG4J2-1874:
Github user remkop commented on the issu
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1528#comment-1528
]
Gary Gregory commented on LOG4J2-1896:
--
Just so I understand: Do you want this ticke
Github user remkop commented on the issue:
https://github.com/apache/logging-log4j2/pull/71
I'm not done reviewing yet but I found two issues:
* StringBuilderEncoder used to have ThreadLocal,
ThreadLocal and ThreadLocal fields, now has one
ThreadLocal field. In the original
On May 7, 2017 9:02 AM, "Remko Popma" wrote:
Ralph, thanks for the transparency!
I'm okay with that unless another tool gives a large advantage. I really
like Gradle's incremental build feature but I can live without it. However,
moving half the project into separate repos feels too much like wo
Ralph, thanks for the transparency!
I'm okay with that unless another tool gives a large advantage. I really
like Gradle's incremental build feature but I can live without it. However,
moving half the project into separate repos feels too much like working
around the limitations of the build tool.
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/logging-log4j2/pull/76
try to fix build on travis
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PascalSchumacher/logging-log4j2
try_to_fix_travis
A
[
https://issues.apache.org/jira/browse/LOG4J2-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999739#comment-15999739
]
Remko Popma commented on LOG4J2-1896:
-
Understood, let's revisit later. Would you min
53 matches
Mail list logo
