Re: Log4j 2.14.0 release status

2020-11-03 Thread Matt Sicker
You should be able to either skip the plug-in in all the modules themselves or maybe there’s a way to configure it only for the parent module without children inheriting it? On Tue, Nov 3, 2020 at 01:05 Ralph Goers wrote: > I had upgraded my Java from Oracle Java 1.8.0_144 to Amazon Corretto >

Re: Log4j 2.14.0 release status

2020-11-02 Thread Ralph Goers
I had upgraded my Java from Oracle Java 1.8.0_144 to Amazon Corretto 1.8.0_272-b10. After downgrading back the error no longer occurs so something has changed in Java itself to cause this. I also get the same error with AdoptOpenJDK 1.8.0_272-b10 and Oracle JDK 1.8.0_271-b09. I do not get the

Re: Log4j 2.14.0 release status

2020-11-02 Thread Ralph Goers
Infra removed all the snapshots and I validated that the generated doap file no longer has the snapshots in it, but the plugin is still failing with "java.lang.IllegalArgumentException: Invalid version number: Version number may be negative or greater than 255”. I’ve created a Jira issue for

Re: Log4j 2.14.0 release status

2020-11-01 Thread Matt Sicker
Well at least it's not an ongoing problem with the new setup. I wonder how that got there... On Sun, 1 Nov 2020 at 10:45, Ralph Goers wrote: > > Yes, Nexus indicates the bad snapshot was pushed by “CI Hudson” in May. > > Ralph > > > On Nov 1, 2020, at 8:23 AM, Matt Sicker wrote: > > > > Are

Re: Log4j 2.14.0 release status

2020-11-01 Thread Ralph Goers
Infra has done nothing with https://issues.apache.org/jira/browse/INFRA-21060 so unless I remove the doap plugin from the site build you have plenty of time. Ralph > On Nov 1, 2020, at 8:30 AM, Carter Kozak wrote: > > I’d like to get a fix

Re: Log4j 2.14.0 release status

2020-11-01 Thread Ralph Goers
Yes, Nexus indicates the bad snapshot was pushed by “CI Hudson” in May. Ralph > On Nov 1, 2020, at 8:23 AM, Matt Sicker wrote: > > Are these snapshots any different from the ones being pushed by our old > Jenkins config? That’s another possibility. I think you’re right about the > repo groups

Re: Log4j 2.14.0 release status

2020-11-01 Thread Carter Kozak
I’d like to get a fix for LOG4J2-2954 into this release so appenders are flushed before the jvm exits. I’ll be reviewing the proposed fix and making required changes tonight or tomorrow if that’s alright. -ck > On Nov 1, 2020, at 8:10 AM, Gary Gregory wrote: > > Over at Apache Commons, I

Re: Log4j 2.14.0 release status

2020-11-01 Thread Matt Sicker
Are these snapshots any different from the ones being pushed by our old Jenkins config? That’s another possibility. I think you’re right about the repo groups though since that’s how Nexus works. On Sun, Nov 1, 2020 at 09:21 Apache wrote: > The public repo is most likely a group repo configured

Re: Log4j 2.14.0 release status

2020-11-01 Thread Apache
The public repo is most likely a group repo configured with both the release repo and the snapshot repo.that way by configuring Maven to use the public repo builds can access both releases and snapshots. But all the snapshots only exist in the snapshot repo. Ralph > On Nov 1, 2020, at 6:08

Re: Log4j 2.14.0 release status

2020-11-01 Thread Gary Gregory
Over at Apache Commons, I just released VFS, and it too is full of snapshots: https://repository.apache.org/content/groups/public/org/apache/commons/commons-vfs2/ Either we have all been doing releases wrong, the tooling is wrong, or our understanding of

Re: Log4j 2.14.0 release status

2020-11-01 Thread Gary Gregory
Very odd indeed, the public (non-snapshot) repository is full of snapshots: https://repository.apache.org/content/groups/public/org/apache/logging/log4j/log4j-core/ Gary On Sun, Nov 1, 2020, 00:51 Ralph Goers wrote: > I started the process of preparing for the release today. The Maven site >

Re: Log4j 2.14.0 release status

2020-10-31 Thread Ralph Goers
I should clarify that it is the DOAP plugin that is failing. It is invoked from the site plugin. Ralph > On Oct 31, 2020, at 9:51 PM, Ralph Goers wrote: > > I started the process of preparing for the release today. The Maven site > build is failing because somehow a version named

Log4j 2.14.0 release status

2020-10-31 Thread Ralph Goers
I started the process of preparing for the release today. The Maven site build is failing because somehow a version named 2.14.0—SNAPSHOT was uploaded to the Nexus Snapshot repository. While investigating I noticed that there is at least one snapshot for every past release so Nexus apparently