[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904613#comment-15904613
]
Seweryn Habdank-Wojewodzki edited comment on LOG4J2-1841 at 3/10/17 7:33 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904613#comment-15904613
]
Seweryn Habdank-Wojewodzki edited comment on LOG4J2-1841 at 3/10/17 7:32 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904613#comment-15904613
]
Seweryn Habdank-Wojewodzki edited comment on LOG4J2-1841 at 3/10/17 7:31 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904613#comment-15904613
]
Seweryn Habdank-Wojewodzki commented on LOG4J2-1841:
Thanks a lot for
[
https://issues.apache.org/jira/browse/LOG4J2-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904066#comment-15904066
]
ASF GitHub Bot commented on LOG4J2-1840:
GitHub user zdiscov opened a pull reques
Guten Tag Ralph Goers,
am Donnerstag, 9. März 2017 um 19:24 schrieben Sie:
> We use general as mainly an announcement list for topics that might
> be of general interest to all logging projects. Generally, these are just
> release announcements.
And "general-dev@" is not an option because one ca
[
https://issues.apache.org/jira/browse/LOG4J2-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihhail Lapushkin updated LOG4J2-1842:
--
Description:
I've been using a modified version of {{SystemPropertiesLookup}} in my pro
We use general as mainly an announcement list for topics that might be of
general interest to all logging projects. Generally, these are just release
announcements.
Ralph
> On Mar 9, 2017, at 10:37 AM, Matt Sicker wrote:
>
> Yeah, I agree that the user lists can remain separate as it doesn't
[
https://issues.apache.org/jira/browse/LOG4J2-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihhail Lapushkin updated LOG4J2-1842:
--
Description:
https://github.com/apache/logging-log4j2/pull/64
I've been using a modifi
[
https://issues.apache.org/jira/browse/LOG4J2-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihhail Lapushkin updated LOG4J2-1842:
--
Description:
https://github.com/apache/logging-log4j2/pull/64
I've been using a modifi
[
https://issues.apache.org/jira/browse/LOG4J2-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903549#comment-15903549
]
ASF GitHub Bot commented on LOG4J2-1842:
GitHub user mihhail-lapushkin opened a p
I am still a bit lost. Maybe it's better if Matt does it?
On Thu, Mar 9, 2017 at 5:22 PM, Ralph Goers
wrote:
> The distribution zip and tarball contain all the artifacts that are being
> released - i.e. the jars. The Log4j distribution includes all the jars
> from all the sub projects. Obviousl
Yeah, I agree that the user lists can remain separate as it doesn't cause
any issues currently. The main idea here is whether we should merge the dev
lists into one, or if we need a common dev list for all devs to subscribe
to (general@ doesn't sound appropriate, but I don't know what that list is
[
https://issues.apache.org/jira/browse/LOG4J2-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zilong Song updated LOG4J2-1843:
Description: The [LOG4J2-1838] issue provide us with the feature to print a
common suffix to each l
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903451#comment-15903451
]
Matt Sicker commented on LOG4J2-1841:
-
This is clearly a bug, yes. We should roll it
[
https://issues.apache.org/jira/browse/LOG4J2-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zilong Song updated LOG4J2-1843:
Description: The [LOG4J2-1838] issue provide us the feature to print a
common suffix to each line o
[
https://issues.apache.org/jira/browse/LOG4J2-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903435#comment-15903435
]
ASF GitHub Bot commented on LOG4J2-1843:
Github user xnslong commented on the iss
[
https://issues.apache.org/jira/browse/LOG4J2-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zilong Song updated LOG4J2-1843:
Summary: Line-wise common suffix support for %ex pattern (was: Line-wise
common suffix support for
Zilong Song created LOG4J2-1843:
---
Summary: Line-wise common suffix support for %throwable pattern
Key: LOG4J2-1843
URL: https://issues.apache.org/jira/browse/LOG4J2-1843
Project: Log4j 2
Issue
You should note that while we consider all votes only PMC votes are “binding”.
I don’t think that changes much however.
From a PMC perspective I have to say that keeping the user’s lists separate
isn’t likely to be an issue as most of the things that would need to be
discussed would be on a dev
The distribution zip and tarball contain all the artifacts that are being
released - i.e. the jars. The Log4j distribution includes all the jars from
all the sub projects. Obviously, the Scala distribution will only contain the
Scala jars. So the assembly xml file needs to be modified to only
I am a bit lost here.
On Thu, Mar 9, 2017 at 4:56 PM, Mikael Ståldal
wrote:
> Change to what?
>
> On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers
> wrote:
>
>> The instructions for what will be in the zip and tar balls will have to
>> change.
>>
>> Ralph
>>
>> On Mar 9, 2017, at 8:01 AM, Matt Sicke
Change to what?
On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers
wrote:
> The instructions for what will be in the zip and tar balls will have to
> change.
>
> Ralph
>
> On Mar 9, 2017, at 8:01 AM, Matt Sicker wrote:
>
> If you have time before the weekend, you could try copying over the
> log4j-dis
The instructions for what will be in the zip and tar balls will have to change.
Ralph
> On Mar 9, 2017, at 8:01 AM, Matt Sicker wrote:
>
> If you have time before the weekend, you could try copying over the
> log4j-distribution section from the main pom files. The "release" maven
> profile sh
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903224#comment-15903224
]
Ralph Goers commented on LOG4J2-1841:
-
Yes, this sounds pretty serous to me too.
> P
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903193#comment-15903193
]
Remko Popma commented on LOG4J2-1841:
-
Sounds like we should roll back LOG4J2-248. Ma
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903170#comment-15903170
]
Matt Sicker commented on LOG4J2-1841:
-
A workaround is mentioned in the
[faq|https:/
If you have time before the weekend, you could try copying over the
log4j-distribution section from the main pom files. The "release" maven
profile should activate it I believe, so you should see the generated zips
and tarballs.
On 9 March 2017 at 03:01, Mikael Ståldal wrote:
> Nice! Tell me if
[
https://issues.apache.org/jira/browse/LOG4J2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Gribov closed LOG4J2-1835.
-
[~jvz], I've built site from master and all seems ok. Thank you.
> Incorrect license info fo
Mihhail Lapushkin created LOG4J2-1842:
-
Summary: Expand SystemPropertiesLookup syntax
Key: LOG4J2-1842
URL: https://issues.apache.org/jira/browse/LOG4J2-1842
Project: Log4j 2
Issue Type:
The votes are way too scattered over the different mailing lists so that
I didn't even find my own vote. ;-) Therefore I'm trying to summarize
the current state of the vote:
log4j-dev@, log4php-dev@, log4net-dev@, log4cxx-dev@ ->d...@logging.apache.org
Matt Sicker: +1
Ralph Goers: +1
Stefan Bo
[
https://issues.apache.org/jira/browse/LOG4J2-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seweryn Habdank-Wojewodzki updated LOG4J2-1841:
---
Description:
Situation till Log4j v. 2.5 (including it):
1. One inst
Nice! Tell me if there is anything I can do to help out.
On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker wrote:
> We've established that this will need to be released before we can
> officially remove the equivalent modules from the main log4j repository
> (and release cycle). Since the artifacts ar
33 matches
Mail list logo
