[ 
https://issues.apache.org/jira/browse/SOLR-16508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Risden updated SOLR-16508:
--------------------------------
    Description: 
To upgrade the build system to the latest gradle version, I ran the following 
command:
{code:java}
./gradlew wrapper --gradle-version 7.5.1{code}

Gradle 7.6.x should support Java 19 - 

 

  was:
To upgrade the build system to the latest gradle version, I ran the following 
command after installing the gradle snap on my system:
{code:java}
gradle wrapper --gradle-version 7.5.1{code}
Then I had to update the version number to 7.5.1 in two files relative to the 
root of the repo's working dir:
{code:java}
gradle/validation/check-environment.gradle
gradle/wrapper/gradle-wrapper.jar.version{code}
Doing that resulted in the attached patch.

I tested with "./gradlew precommit -Pvalidation.git.failOnModified=false" on 
branch_9x and main with OpenJDK 17 after I did this upgrade.  Both passed.  
Does it need any more validation before committing to main?  Is it something 
that should be backported to branch_9x?

This gradle upgrade gets us Java 18 support, but not Java 19.

 


> Upgrade gradle wrapper to 7.6
> -----------------------------
>
>                 Key: SOLR-16508
>                 URL: https://issues.apache.org/jira/browse/SOLR-16508
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build
>    Affects Versions: 9.0, 9.1
>            Reporter: Kevin Risden
>            Assignee: Kevin Risden
>            Priority: Minor
>
> To upgrade the build system to the latest gradle version, I ran the following 
> command:
> {code:java}
> ./gradlew wrapper --gradle-version 7.5.1{code}
> Gradle 7.6.x should support Java 19 - 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to