Re: [VOTE] Release Log4j 2.9.0-rc1

You just commit the changed files to the svn repo where the site is located. I forget which repo it is, but there was a notification email recently from when Ralph committed the site a couple days ago. On 1 September 2017 at 04:32, Mikael Ståldal wrote: > Yes, that part I know. But how do I then

Re: [VOTE] Release Log4j 2.9.0-rc1

Yes, that part I know. But how do I then publish the web site? On 2017-08-31 22:17, Ralph Goers wrote: That is actually documented in the original release vote email. a) for a new copy do "git clone https://git-wip-us.apache.org/repos/asf/logging-log4j2.git

Re: [VOTE] Release Log4j 2.9.0-rc1

That is actually documented in the original release vote email. a) for a new copy do "git clone https://git-wip-us.apache.org/repos/asf/logging-log4j2.git

Re: [VOTE] Release Log4j 2.9.0-rc1

How can I do that? On 2017-08-28 18:18, Ralph Goers wrote: Oh, and if you check out from the release tag and create a branch the web site fixes can be made there after the release is complete.

Re: [VOTE] Release Log4j 2.9.0-rc1

Please create a Jira issue for this. It should be a simple matter to catch the exception and ignore it. Ralph > On Aug 30, 2017, at 2:56 PM, Leon Finker wrote: > > Hi, > > Tested with two large legacy projects. The only issue found due to xerces > 2.6.2 version being pulled in in one app and

Re: [VOTE] Release Log4j 2.9.0-rc1

Hi, Tested with two large legacy projects. The only issue found due to xerces 2.6.2 version being pulled in in one app and then causing log4j2 failure to initialize (changes are from LOG4J2-1959). I guess we may have to try and upgrade xerces to latest due to this. Exception in thread "main" java

Re: [VOTE] Release Log4j 2.9.0-rc1

If anyone has a script for recursively checking the checksums of a directory tree I'd be much obliged. (Shameless plug) Every java main() method deserves http://picocli.info > On Aug 30, 2017, at 14:36, Ralph Goers wrote: > > Here is my +1 > > Ralph > >> On Aug 26, 2017, at 7:45 PM, Ralph G

Re: [VOTE] Release Log4j 2.9.0-rc1

Here is my +1 Ralph > On Aug 26, 2017, at 7:45 PM, Ralph Goers wrote: > > 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...

Re: [VOTE] Release Log4j 2.9.0-rc1

+1 Tested with Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T01:41:47+09:00) Maven home: C:\apps\apache-maven-3.3.9\bin\.. Java version: 1.8.0_131, vendor: Oracle Corporation Java home: C:\apps\jdk1.8.0_131\jre Default locale: en_US, platform encoding: MS932 OS name: "wi

Re: [VOTE] Release Log4j 2.9.0-rc1

Testing with: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: /opt/apache-maven-3.3.9 Java version: 1.8.0_144, vendor: Oracle Corporation Java home: /opt/jvm/jdk1.8.0_144/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", ve

Re: [VOTE] Release Log4j 2.9.0-rc1

On 28 August 2017 at 14:27, Mikael Ståldal wrote: > Oops, fixed in master branch now. > > I changed pom.xml and doap_log4j2.rdf, is that all? That's all the places I know of. Thanks! > > > > On 2017-08-28 17:51, Matt Sicker wrote: > >> * Mikael still works for Magine TV on the team page; he s

Re: [VOTE] Release Log4j 2.9.0-rc1

Oops, fixed in master branch now. I changed pom.xml and doap_log4j2.rdf, is that all? On 2017-08-28 17:51, Matt Sicker wrote: * Mikael still works for Magine TV on the team page; he should update his organization. ;)

Re: [VOTE] Release Log4j 2.9.0-rc1

Do note that you cannot build with Docker from a src zip file. Gary On Mon, Aug 28, 2017 at 9:51 AM, Matt Sicker wrote: > +1 > > Builds fine with Java 8 and 9 (tried originally with Zulu 8u144 and JDK 9 > EA +181) on macOS 10.12. Also builds fine in Docker. > > Signatures are all good. > > Mave

Re: [VOTE] Release Log4j 2.9.0-rc1

On Mon, Aug 28, 2017 at 10:17 AM, Ralph Goers wrote: > Thanks Matt. I agree that we should stick with 2.x.x from here on out. > Whoever modified the version in changes.xml set it to 2.9.0 so I just > followed suit. > That would be me ;-) Gary > > Ralph > > > On Aug 28, 2017, at 8:51 AM, Matt

Re: [VOTE] Release Log4j 2.9.0-rc1

Oh, and if you check out from the release tag and create a branch the web site fixes can be made there after the release is complete. Ralph > On Aug 28, 2017, at 8:51 AM, Matt Sicker wrote: > > +1 > > Builds fine with Java 8 and 9 (tried originally with Zulu 8u144 and JDK 9 > EA +181) on macO

Re: [VOTE] Release Log4j 2.9.0-rc1

Thanks Matt. I agree that we should stick with 2.x.x from here on out. Whoever modified the version in changes.xml set it to 2.9.0 so I just followed suit. Ralph > On Aug 28, 2017, at 8:51 AM, Matt Sicker wrote: > > +1 > > Builds fine with Java 8 and 9 (tried originally with Zulu 8u144 and J

Re: [VOTE] Release Log4j 2.9.0-rc1

I should also add this note to my +1: I have been testing SNAPSHOT builds for a couple of weeks waiting on 2.9.0, so I am pretty confident WRT stability. Gary On Mon, Aug 28, 2017 at 9:51 AM, Matt Sicker wrote: > +1 > > Builds fine with Java 8 and 9 (tried originally with Zulu 8u144 and JDK 9 >

Re: [VOTE] Release Log4j 2.9.0-rc1

+1 Builds fine with Java 8 and 9 (tried originally with Zulu 8u144 and JDK 9 EA +181) on macOS 10.12. Also builds fine in Docker. Signatures are all good. Maven artifacts work with my tested applications (which are Scala 2.12 applications using SBT 0.13.16 with log4j-api-scala 11.0 as well). No

Re: [VOTE] Release Log4j 2.9.0-rc1

I do like the full version number, but I'm just comparing to historical releases: https://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.logging.log4j%22%20AND%20a%3A%22log4j-api%22 On 28 August 2017 at 10:17, Gary Gregory wrote: > It sorts pertier? > > On Mon, Aug 28, 2017 at 9:15 AM,

Re: [VOTE] Release Log4j 2.9.0-rc1

It sorts pertier? On Mon, Aug 28, 2017 at 9:15 AM, Matt Sicker wrote: > Any particular reason this is tagged as 2.9.0 instead of 2.9? > > On 27 August 2017 at 19:03, Matt Sicker wrote: > > > > > > > On 27 August 2017 at 11:23, Ralph Goers > > wrote: > > > >> Matt added an exclude for the docke

Re: [VOTE] Release Log4j 2.9.0-rc1

Any particular reason this is tagged as 2.9.0 instead of 2.9? On 27 August 2017 at 19:03, Matt Sicker wrote: > > > On 27 August 2017 at 11:23, Ralph Goers > wrote: > >> Matt added an exclude for the docker file back before the 2.8. release. >> I’m not sure why. >> > > I don't remember exactly w

Re: [VOTE] Release Log4j 2.9.0-rc1

On 27 August 2017 at 11:23, Ralph Goers wrote: > Matt added an exclude for the docker file back before the 2.8. release. > I’m not sure why. > I don't remember exactly why, but my guess is a rat-check error. The license header wasn't added until after 2.8 according to the tags: https://github.c

Re: [VOTE] Release Log4j 2.9.0-rc1

The KEYS file is where it has been since 2013 - https://dist.apache.org/repos/dist/release/logging/KEYS . This is documented at http://logging.apache.org/log4j/2.x/download.html . Ralph

Re: [VOTE] Release Log4j 2.9.0-rc1

+1 See my previous messages for details. Tested with: Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T13:39:06-06:00) Maven home: C:\Java\apache-maven-3.5.0\bin\.. Java version: 1.7.0_80, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_80\jre Default

Re: [VOTE] Release Log4j 2.9.0-rc1

With regard to the CLIRR report: 1. The change the return type from a MapMessage to a StructuredDataMessage was done by you on June 6. It isn’t clear why you did that. However, I don’t see how this change could cause any problems since a StructuredDataMessage is a MapMessage. 2. The second chang

Re: [VOTE] Release Log4j 2.9.0-rc1

On Sun, Aug 27, 2017 at 8:12 AM, Gary Gregory wrote: > From src zip file and using guidance from BUILDING.md > > ASC, MD5, SHA1, OK. > > RAT check OK > > mvn clean install OK > > CLIRR check OK but MUST be done AFTER the above and I get: > > [INFO] --- clirr-maven-plugin:2.8:check (default-cli) @

Re: [VOTE] Release Log4j 2.9.0-rc1

On Sun, Aug 27, 2017 at 8:12 AM, Gary Gregory wrote: > From src zip file and using guidance from BUILDING.md > > ASC, MD5, SHA1, OK. > FYI: I was able to validate against a KEYS file I imported previously. Gary > > RAT check OK > > mvn clean install OK > > CLIRR check OK but MUST be done AFTER

Re: [VOTE] Release Log4j 2.9.0-rc1

Matt added an exclude for the docker file back before the 2.8. release. I’m not sure why. Ralph > On Aug 27, 2017, at 7:50 AM, Gary Gregory wrote: > > Minor bug but not a blocker: the Dockerfile is missing from the src > distribution zip. > > Gary > > On Sat, Aug 26, 2017 at 8:45 PM, Ralph G

Re: [VOTE] Release Log4j 2.9.0-rc1

Minor bug but not a blocker: the Dockerfile is missing from the src distribution zip. Gary On Sat, Aug 26, 2017 at 8:45 PM, Ralph Goers wrote: > 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 developer

Re: [VOTE] Release Log4j 2.9.0-rc1

>From src zip file and using guidance from BUILDING.md ASC, MD5, SHA1, OK. RAT check OK mvn clean install OK CLIRR check OK but MUST be done AFTER the above and I get: [INFO] --- clirr-maven-plugin:2.8:check (default-cli) @ log4j-api --- [INFO] artifact org.apache.logging.log4j:log4j-api: chec

Re: [VOTE] Release Log4j 2.9.0-rc1

Link to KEYS file please? Gary On Sat, Aug 26, 2017 at 8:45 PM, Ralph Goers wrote: > 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 releas

[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