[
https://issues.apache.org/jira/browse/LUCENE-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gautam Worah updated LUCENE-9990:
---------------------------------
Description:
Gradle 7 has added support for running builds with arbitrary JVMs.
Today, Gradle 6 only supports running tests with Java 16 and so on.
I tried to upgrade our Gradle version to 7 and made some progress.
1. Removed the JavaInstallationRegistry plugin because it is deprecated in
Gradle 7 ( a simple build scan reveals this). This is replaced by the toolchain
support added in Gradle 7 and works great. JavaInstallationRegistry is the only
deprecated plugin
2. Building Lucene with Java 16 gives some weird error when trying to access
internal JVM classes. Fixing it with {{--add-opens}} does the trick. Related
Github issue: [https://github.com/gradle/gradle/issues/15538]
What does not work?
As noted by [~dweiss]
[here|https://github.com/palantir/gradle-consistent-versions/issues/700], the
gradle-consistent-versions plugin does not support Gradle 7. There was a
related [PR|https://github.com/palantir/gradle-consistent-versions/pull/721]
but it still a WIP
Attached is a WIP patch that breaks due to the gradle-consistent-versions plugin
was:
Gradle 7 has added support for running builds with arbitrary JVMs.
Today, Gradle 6 only supports running tests with Java 16 and so on.
I tried to upgrade our Gradle version to 7 and made some progress.
1. Removed the JavaInstallationRegistry plugin because it is deprecated in
Gradle 7 ( a simple build scan reveals this). This is replaced by the toolchain
support added in Gradle 7 and works great. JavaInstallationRegistry is the only
deprecated plugin
2. Building Lucene with Java 16 and it gives some weird error when trying to
access internal JVM classes. Fixing it with {{--add-opens}} does the trick.
Related Github issue: [https://github.com/gradle/gradle/issues/15538]
What does not work?
As noted by [~dweiss]
[here|https://github.com/palantir/gradle-consistent-versions/issues/700], the
gradle-consistent-versions plugin does not support Gradle 7. There was a
related [PR|https://github.com/palantir/gradle-consistent-versions/pull/721]
but it still a WIP
Attached is a WIP patch that breaks due to the gradle-consistent-versions plugin
> Tracking issue for Gradle upgrade to 7.0.2
> ------------------------------------------
>
> Key: LUCENE-9990
> URL: https://issues.apache.org/jira/browse/LUCENE-9990
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Gautam Worah
> Priority: Minor
> Attachments: wip_gradle7_upgrade_patch
>
>
> Gradle 7 has added support for running builds with arbitrary JVMs.
> Today, Gradle 6 only supports running tests with Java 16 and so on.
> I tried to upgrade our Gradle version to 7 and made some progress.
> 1. Removed the JavaInstallationRegistry plugin because it is deprecated in
> Gradle 7 ( a simple build scan reveals this). This is replaced by the
> toolchain support added in Gradle 7 and works great. JavaInstallationRegistry
> is the only deprecated plugin
> 2. Building Lucene with Java 16 gives some weird error when trying to access
> internal JVM classes. Fixing it with {{--add-opens}} does the trick. Related
> Github issue: [https://github.com/gradle/gradle/issues/15538]
> What does not work?
> As noted by [~dweiss]
> [here|https://github.com/palantir/gradle-consistent-versions/issues/700], the
> gradle-consistent-versions plugin does not support Gradle 7. There was a
> related [PR|https://github.com/palantir/gradle-consistent-versions/pull/721]
> but it still a WIP
>
> Attached is a WIP patch that breaks due to the gradle-consistent-versions
> plugin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
