-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Java 17 in Gradle Task #17782
Comments
Hi, @fte7fe, thanks for reporting this issue, we will work on it. |
Hi @fte7fe, PR has been merged. |
Hi @LiliaSabitova , I would like to know how long it will take to have the selection available in gradle devops task? |
Same question here. I am setting up a new project and I don't want to work around this issue for just a few weeks. |
Same question - Java 17 is the latest LTS, but do not see a way to configure it - latest seems to be JDK 11 ? |
@breucode Looks like it can still be configured in the pipeline, the official docs are not updated: #15647 (comment) |
Question, Bug, or Feature?
Type: Feature
Enter Task Name: Gradle
list here (V# not needed):
https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/GradleV3
Environment
Server - Azure Pipelines or TFS on-premises?
Agent - Hosted or Private:
Issue Description
As mentioned in https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/gradle-v3?view=azure-pipelines
And also what you see if you configure the task, there is no option to use jdk 17 with gradle, the maven task already support jdk17 for instance.
There are already PR for this but those have been marked as stale :
#16458
#16160
The maven PR is the following:
#15844
There seem to be a workaround documented here , could be nice in the documentation : #15647
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]
The text was updated successfully, but these errors were encountered: