[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322038#comment-15322038
]
Anthony Maire commented on LOG4J2-1397:
---
At first sight, this approach may work cor
[
https://issues.apache.org/jira/browse/LOG4J2-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-849:
---
Fix Version/s: (was: 2.6.1)
2.7
> [Perf] Add performance tests to compare overh
[
https://issues.apache.org/jira/browse/LOG4J2-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1013:
Fix Version/s: (was: 2.6.1)
2.7
> Log4j2 Main Arguments Lookup by name doesn
[
https://issues.apache.org/jira/browse/LOG4J2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1381:
Fix Version/s: (was: 2.6.1)
2.7
> Documentation for LoggerNameLevelRewritePo
[
https://issues.apache.org/jira/browse/LOG4J2-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1130:
Fix Version/s: (was: 2.6.1)
2.7
> CsvLogEventLayout NanoTime timestamp is al
[
https://issues.apache.org/jira/browse/LOG4J2-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1116:
Fix Version/s: (was: 2.6.1)
2.7
> Web app-friendly thread locals for gc-free
[
https://issues.apache.org/jira/browse/LOG4J2-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-915:
---
Fix Version/s: (was: 2.6.1)
2.7
> Wrong timestamp of filename when SizeBasedTri
[
https://issues.apache.org/jira/browse/LOG4J2-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1229:
Fix Version/s: (was: 2.6.1)
2.7
> Error creating logger
> --
[
https://issues.apache.org/jira/browse/LOG4J2-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1198:
Fix Version/s: (was: 2.6.1)
2.7
> Add support for custom rollover strategy
>
[
https://issues.apache.org/jira/browse/LOG4J2-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1086:
Fix Version/s: (was: 2.6.1)
2.7
> SizeBasedTriggeringPolicy is not working p
[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321679#comment-15321679
]
Remko Popma edited comment on LOG4J2-1397 at 6/9/16 6:33 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321905#comment-15321905
]
Gary Gregory commented on LOG4J2-1418:
--
For example: org.apache.logging.log4j.jul.Ap
The vote has passed with binding +1 votes from Remko Popma, Matt Sicker, Gary
Gregory and Ralph Goers. Leon Finker also cast a +1 vote.
Thanks to all who voted.
I will continue on with the release process.
Ralph
My +1
Ralph
> On Jun 5, 2016, at 6:55 PM, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.6.1, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
>
I just tried to do a full build and got this test to hang. Gary reported the
same thing last week on Windows. The stack trace indicates that it isn’t
properly shutting down. Somehow it seems the BlockingAppender must not be
having its shutdown flag set. This test was only added a month ago. I’m
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321700#comment-15321700
]
Gary Gregory commented on LOG4J2-1418:
--
Sure, but we should also audit our use of {{
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321691#comment-15321691
]
Remko Popma commented on LOG4J2-1418:
-
That log method is for the StatusLogger. I did
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321691#comment-15321691
]
Remko Popma edited comment on LOG4J2-1418 at 6/9/16 12:23 AM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321674#comment-15321674
]
Gary Gregory edited comment on LOG4J2-1418 at 6/9/16 12:17 AM:
[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321679#comment-15321679
]
Remko Popma commented on LOG4J2-1397:
-
The byte buffer should not be used by two thre
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321674#comment-15321674
]
Gary Gregory commented on LOG4J2-1418:
--
We are not GC-free, I claim, even in the sce
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321614#comment-15321614
]
Remko Popma commented on LOG4J2-1418:
-
Can we add this as a protected method to Abstr
[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321285#comment-15321285
]
Anthony Maire commented on LOG4J2-1397:
---
Basically, a layout that have a dependency
FYI: I pushed the 2.6 tag to git.
Gary
On Wed, Jun 8, 2016 at 11:24 AM, Ralph Goers
wrote:
> The project-info-reports:scm goal accepts scmTag as a parameter so we
> should be able to configure that as
>
> log4j-${log4jReleaseVersion}
>
> I’ll have to try it though to see if that is actually the
The project-info-reports:scm goal accepts scmTag as a parameter so we should be
able to configure that as
log4j-${log4jReleaseVersion}
I’ll have to try it though to see if that is actually the goal that generates
that page and to see if it breaks anything else.
Ralph
> On Jun 8, 2016, at 11:
Note that even if you add the tag the web site is still going to point to the
rc tag unless the page is manually modified. Maven creates the source
repository page automatically and uses the tag that was checked out. We would
have to investigate to see if there is some way to override that.
Ral
On Wed, Jun 8, 2016 at 7:17 AM, Matt Sicker wrote:
> Well, the highest number RC would normally be the release, and we haven't
> skipped any releases, right?
>
But why bother with the guess work?
I'll create a tag for 2.6... ;-)
Gary
>
> On 8 June 2016 at 00:28, Gary Gregory wrote:
>
>> We
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320932#comment-15320932
]
Gary Gregory commented on LOG4J2-1418:
--
Is this as simple as adding a getMessageFact
Created a JIRA issue for this:
https://issues.apache.org/jira/browse/LOG4J2-1418
On Fri, Jun 3, 2016 at 7:27 PM, Mikael Ståldal
wrote:
> That was an idea, not something already in the code.
>
> On Fri, Jun 3, 2016 at 6:53 PM, Gary Gregory
> wrote:
>
>> On Fri, Jun 3, 2016 at 9:10 AM, Gary Grego
[
https://issues.apache.org/jira/browse/LOG4J2-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal updated LOG4J2-1418:
---
Description:
It would be useful for a custom Logger implementation to be able to get hold of
Mikael Ståldal created LOG4J2-1418:
--
Summary: Provide MessageFactory2 to custom Logger implementations
Key: LOG4J2-1418
URL: https://issues.apache.org/jira/browse/LOG4J2-1418
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320790#comment-15320790
]
Mikael Ståldal commented on LOG4J2-1395:
Strange. I just tried again on my Linux
[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320744#comment-15320744
]
Mikael Ståldal commented on LOG4J2-1397:
So the async logger should copy the appl
Well, the highest number RC would normally be the release, and we haven't
skipped any releases, right?
On 8 June 2016 at 00:28, Gary Gregory wrote:
> We should. If a RC does NOT lead to a release, then how can you tell that
> from one that did?
>
> Gary
>
> On Tue, Jun 7, 2016 at 10:05 PM, Ralph
[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320181#comment-15320181
]
Mikael Ståldal commented on LOG4J2-1397:
Thanks, it's helpful to get this kind of
[
https://issues.apache.org/jira/browse/LOG4J2-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320175#comment-15320175
]
Anthony Maire commented on LOG4J2-1397:
---
Here is my usecase:
- The application is r
36 matches
Mail list logo
