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 error with Oracle Java 1.8.0_202-b08.
I will run the build using the Oracle 202 version of Java 8 to get around the problem. But before I run the build I want to see if there is a way to skip the doap plugin in subprojects as it is really slow and is unnecessary in those. Ralph > On Nov 2, 2020, at 9:13 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > 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 the doap > plugin. > > Ralph > >> On Nov 1, 2020, at 10:21 AM, Matt Sicker <boa...@gmail.com> wrote: >> >> 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 <ralph.go...@dslextreme.com> 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 <boa...@gmail.com> 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 though since that’s how Nexus works. >>>> >>>> On Sun, Nov 1, 2020 at 09:21 Apache <ralph.go...@dslextreme.com> wrote: >>>> >>>>> 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 AM, Gary Gregory <garydgreg...@gmail.com> wrote: >>>>>> >>>>>> 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 <ralph.go...@dslextreme.com> >>>>> wrote: >>>>>>> >>>>>>> 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 is not configured to delete snapshots after a release is >>>>>>> performed. >>>>>>> >>>>>>> I’ve asked in Slack to have all the snapshots under logging be deleted >>>>> but >>>>>>> I suspect I will need to create a Jira issue. In my experience Jira >>>>> isn’t >>>>>>> especially quick about acting on these so I don’t know when I will be >>>>> able >>>>>>> to proceed. Matt or Gary, if you have more karma then me for some reason >>>>>>> please see what you can do. >>>>>>> >>>>>>> Ralph >>>>>>> >>>>> >>>>> >>>>> >>> >>> >> > > >
