Skip to content

Remove JavadocSafeJavaBuildVersion from the base ci.yml template once all libraries support Java 21 Javadoc generation #38267

Open

Description

And add a way for libraries that need it to use an earlier Java version for this step.

So far, we have very few libraries supporting Java 21-style Javadocs, so we'll keep the baseline on Java 17 and add exceptions for Java 21-ready libs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Java 21 SupportLabel for tracking issues related to adding support for Java 21 in the Azure SDK for Java.MQThis issue is part of a "milestone of quality" initiative.test-reliabilityIssue that causes tests to be unreliable

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions