[
https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168821#comment-16168821
]
Remko Popma commented on LOG4J2-2051:
-
Should we leave this ticket open, or resolve it with
[
https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-2051:
-
Labels: Java8 (was: )
> Update Conversant Disruptor from 1.2.10 to 1.2.11.
>
[
https://issues.apache.org/jira/browse/LOG4J2-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168818#comment-16168818
]
ASF subversion and git services commented on LOG4J2-2051:
-
Commit
> On Sep 15, 2017, at 11:44 AM, Mikael Ståldal wrote:
>
> It seems like we miss a Git tag for the 2.9.0 release.
Thanks. I forgot to add the tag after the release vote. I will do that. The rc1
tag is there.
Ralph
Using the gitbox integration (I think it's called), we can selectively
enable various GitHub features to synchronize with our main ASF git repo.
Enabling the releases feature of GitHub could be one of them. Infra has
more info somewhere.
On 15 September 2017 at 14:03, Mikael Ståldal
The release checklist is on the wiki:
https://wiki.apache.org/logging/Log4j2ReleaseGuide
I don't think I have an account on there.
On 15 September 2017 at 13:53, Mikael Ståldal wrote:
> We (should) have a link to the latest release in README.md in Git.
> However, that was not
We (should) have a link to the latest release in README.md in Git.
However, that was not updated since 2.8. I have updated it to 2.9.0 now.
We should make sure to update it for every release.
Do we have a release checklist? On that we should add to create a Git
tag, and update README.md.
Github user mdvorak commented on the issue:
https://github.com/apache/logging-log4j2/pull/110
This is build log, it hangs after that.. But i'm not sure why I'm seeing
this exception.
https://gist.github.com/anonymous/9909ea92d10ac4ebe36f27a0610e7c2d
---
[
https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168210#comment-16168210
]
Remko Popma edited comment on LOG4J2-2052 at 9/15/17 5:16 PM:
--
I wasn't
[
https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168210#comment-16168210
]
Remko Popma commented on LOG4J2-2052:
-
I wasn't aware of that fix. We could try to detect the Java
Dan Berindei created LOG4J2-2052:
Summary: Disable thread name caching by default
Key: LOG4J2-2052
URL: https://issues.apache.org/jira/browse/LOG4J2-2052
Project: Log4j 2
Issue Type:
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168059#comment-16168059
]
Remko Popma edited comment on LOG4J2-1988 at 9/15/17 3:52 PM:
--
Fixed in
[
https://issues.apache.org/jira/browse/LOG4J2-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-1914.
-
Resolution: Fixed
Fix Version/s: 2.9.1
Fixed in master.
I was able to add a test that
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168057#comment-16168057
]
ASF subversion and git services commented on LOG4J2-1988:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-1988.
-
Resolution: Fixed
Fix Version/s: 2.9.1
Fixed in master.
I was able to add a test that
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-1988:
Priority: Major (was: Minor)
> java.util.ConcurrentModificationException with AsyncLogger?
>
16 matches
Mail list logo