Took a look on ASF Slack w/ Sanjay and found that the Lucene one has the exports but the Solr one doesn't and its managed at the group level.
https://ci-builds.apache.org/job/Lucene/configfiles/editConfig?id=lucene_gradle.properties vs https://ci-builds.apache.org/job/Solr/configfiles/editConfig?id=solr_gradle.properties Kevin Risden On Wed, Oct 30, 2024 at 10:48 AM Jason Gerlowski <gerlowsk...@gmail.com> wrote: > Hey all, > > Following the recent move to Java 21 on 'main', many of our Jenkins > jobs for that branch are failing with the following message: > > -------- > Execution failed for task ':checkJdkInternalsExportedToGradle'. > > Certain gradle tasks and plugins require access to jdk.compiler > internals, your gradle.properties might have just been generated or could > be out of sync (see gradle/template.gradle.properties) > -------- > > This looks like a quick enough fix - > `gradle/template.gradle.properties` shows how to export JDK internals > by passing a few "--add-exports" flags via the org.gradle.jvmargs > property. > > But I'm unsure how to modify the gradle.properties that our builds > use, which is currently managed through the Jenkins > "config-file-provider" plugin [1] [2]. I can ask INFRA for the > permissions necessary to edit this file, but that may not be the right > approach if the Jenkins-provided gradle.properties is meant to be a > minimal base used by many projects. > > Has anyone else been looking into the JDK21 build failures? Is anyone > familiar with our Jenkins gradle builds and the "managed" file they > use? > > Best, > > Jason > > [1] https://ci-builds.apache.org/job/Solr/job/Solr-Check-main/configure > [2] https://plugins.jenkins.io/config-file-provider/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
