All Commons components are Java 8 (or older), so all could be disabled? I only rely on GitHub builds since it validates PRs. There is a way to make releases from GH but I've not looked into it yet.
Gary On Mon, Mar 20, 2023, 06:17 Alex Herbert <alex.d.herb...@gmail.com> wrote: > A recent update in Jenkins has updated some part of the Jenkins > tooling that reports on the job to a jar file compiled for Java 11. > This is making all the Java 8 Jenkins jobs fail. > > I am not sure of the relevance of many of these Jenkins builds given > the use of GH actions for CI builds. The advantage of Jenkins builds > is to deploy SNAPSHOTS automatically to the snapshot repo. This is > useful for mutli-module projects where you are able to do a build > within one module from the current dev branch and the other > dependencies are pulled from the snapshot repo. It can also be used to > run the SonarCloud code quality analysis. > > I suggest disabling the following builds that are failing due to Java > 11 incompatibility in the job setup: > > - commons-bcel > - commons-build-plugin > - commons-cli > - commons-codec > - commons-configuration > - commons-imaging > - commons-io > - commons-parent > - commons-validator > > The configuration can be fixed if snapshot deployment is required in the > future. > > Alex > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
