[VOTE] Release Log4j 2.9.0-rc1

This is a vote to release Log4j 2.9.0 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... The vote will remain open for 72 hours (or more if required). All votes are welcome

Re: Release build failed

Works for me. I'll wait until the release is finalized. On 26 August 2017 at 17:00, Ralph Goers wrote: > I’d prefer not to add enhancements until after the release vote. > > Ralph > > > On Aug 26, 2017, at 1:58 PM, Matt Sicker wrote: > > > > Sounds good. Do you want me to hold off on merging th

Re: Release build failed

I’d prefer not to add enhancements until after the release vote. Ralph > On Aug 26, 2017, at 1:58 PM, Matt Sicker wrote: > > Sounds good. Do you want me to hold off on merging the LOG4J2-1431 branch? > > On 26 August 2017 at 15:57, Ralph Goers wrote: > >> The release build ran fine the secon

Build failed in Jenkins: Log4j 2.x #3036

See -- [...truncated 4.65 MB...] Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/logging/log4j/log4j/2.9.1-SNAPSHOT/maven-metadata.xml Uploaded: https://re

Build failed in Jenkins: Log4j 2.x #3035

See Changes: [rgoers] [maven-release-plugin] prepare release log4j-2.9-rc1 [rgoers] [maven-release-plugin] prepare for next development iteration -- [...truncated 4.66 MB...]

Re: Release build failed

Sounds good. Do you want me to hold off on merging the LOG4J2-1431 branch? On 26 August 2017 at 15:57, Ralph Goers wrote: > The release build ran fine the second time around. Now I have to verify > it, build the site, etc. > > Ralph > > > On Aug 26, 2017, at 1:20 PM, Ralph Goers > wrote: > > >

Re: Release build failed

The release build ran fine the second time around. Now I have to verify it, build the site, etc. Ralph > On Aug 26, 2017, at 1:20 PM, Ralph Goers wrote: > > The regular build ran fine. I’m trying it again. > > Ralph > >> On Aug 26, 2017, at 1:18 PM, Gary Gregory wrote: >> >> How about tryi

[jira] [Commented] (LOG4J2-1809) Add global configuration environment SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142933#comment-16142933 ] ASF subversion and git services commented on LOG4J2-1809: - Commit

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142930#comment-16142930 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142931#comment-16142931 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142932#comment-16142932 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

[jira] [Commented] (LOG4J2-1809) Add global configuration environment SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142929#comment-16142929 ] ASF subversion and git services commented on LOG4J2-1809: - Commit

Re: Release build failed

The regular build ran fine. I’m trying it again. Ralph > On Aug 26, 2017, at 1:18 PM, Gary Gregory wrote: > > How about trying with Java 8? > > G > > On Aug 26, 2017 14:00, "Matt Sicker" wrote: > >> I don't see anything wrong with that test. Strange. >> >> On 26 August 2017 at 14:45, Ralph

Re: Release build failed

How about trying with Java 8? G On Aug 26, 2017 14:00, "Matt Sicker" wrote: > I don't see anything wrong with that test. Strange. > > On 26 August 2017 at 14:45, Ralph Goers > wrote: > > > The release build failed with something I have never seen before. I am > > going to try a normal build a

Re: Release build failed

I don't see anything wrong with that test. Strange. On 26 August 2017 at 14:45, Ralph Goers wrote: > The release build failed with something I have never seen before. I am > going to try a normal build and see if it works. > > Ralph > > [INFO] [ERROR] Failed to execute goal org.apache.maven.plu

Release build failed

The release build failed with something I have never seen before. I am going to try a normal build and see if it works. Ralph [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on project log4j-core: There are test failures. [INFO] [E

Re: [log4j2] sys props driving me nuts

Alright, feel free to continue on with the release. I have some failing unit tests in this branch that seem to be related to hacky tests that try to avoid cleanups rather than the implementation itself. On 26 August 2017 at 14:31, Ralph Goers wrote: > I moved the test classes that were dependent

Re: [log4j2] sys props driving me nuts

I have restarted the release build. Ralph > On Aug 26, 2017, at 12:29 PM, Matt Sicker wrote: > > Should I update the @since to 2.9.1 then, or is the release on hold for > now? I've got the code working and docs are pretty updated at this point. > > On 26 August 2017 at 14:14, Gary Gregory wro

Re: [log4j2] sys props driving me nuts

I moved the test classes that were dependent on log4j-server to that project. Ralph > On Aug 26, 2017, at 11:27 AM, Ralph Goers wrote: > > Scratch that. It seems Log4j now has a dependency on log4j-server? That must > be released before a release build can be run. Why does the main project hav

Re: [log4j2] sys props driving me nuts

Should I update the @since to 2.9.1 then, or is the release on hold for now? I've got the code working and docs are pretty updated at this point. On 26 August 2017 at 14:14, Gary Gregory wrote: > IMO, the simplest solution is to bring log4j-server back into the main > repo. > > Gary > > On Aug 2

Re: [log4j2] sys props driving me nuts

IMO, the simplest solution is to bring log4j-server back into the main repo. Gary On Aug 26, 2017 12:27, "Ralph Goers" wrote: > Scratch that. It seems Log4j now has a dependency on log4j-server? That > must be released before a release build can be run. Why does the main > project have a depend

Jenkins build is back to normal : Log4j 2.x #3033

See

Re: [log4j2] sys props driving me nuts

Scratch that. It seems Log4j now has a dependency on log4j-server? That must be released before a release build can be run. Why does the main project have a dependency on that? Ralph > On Aug 26, 2017, at 11:21 AM, Ralph Goers wrote: > > > I am just about to start the release build of 2.9 so

Re: [log4j2] sys props driving me nuts

I am just about to start the release build of 2.9 so please hold off on committing. Ralph > On Aug 26, 2017, at 10:54 AM, Matt Sicker wrote: > > I've finally got some time this weekend and am working on merging this > today. Strangely enough, my old branch merged with no git merge conflicts,

Re: [log4j2] sys props driving me nuts

I've finally got some time this weekend and am working on merging this today. Strangely enough, my old branch merged with no git merge conflicts, so it shouldn't be too hard to integrate at this point. I'll be handling documentation updates along with trying to copy over all the old property names

[jira] [Commented] (LOG4J2-2025) Support Tomcat JULI's per-webapp JUL logging by implementing java.util.logging.Handler

[ https://issues.apache.org/jira/browse/LOG4J2-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142704#comment-16142704 ] Ibrahim M. Ghazal commented on LOG4J2-2025: --- Yes, performance will be an issue.

Build failed in Jenkins: Log4j 2.x #3032

See Changes: [rgoers] Update the logo -- [...truncated 4.70 MB...] Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/logging/log4j/log4j-jcl/2

Jenkins build is back to normal : Log4j 2.x #3031

See