You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a library where I still maintain Java 8 compatibility.
But I want JavaDoc to always be created with at least Java 9 to get the nice search box.
So I could configure a Java 9 toolchain for the JavaDoc task of course.
But if someone builds with Java 11, there is not really a need to discover or auto-provision a Java 9 toolchain.
Because of that it would be nice if you could specify a toolchain with min language version (maybe there are also use-cases for max language version), so that the current toolchain is used if it is recent enough and just another one is searched if it is too old.
Currently you would probably have to do something like
While the work-around of course only works if the current version is compatible, a min version and max version would be better as then also another discovered version can be used, like you specify "min java 9", run with java 8, and there is a discovered java 10, then for the JavaDoc task the discovered version can be used without provisioning a new java 9 version.
Maybe even a "preferred version" would make sense then, so if min version is 9 and 9 and 10 is discovered that the preferred one is used, but that might be overkill.
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.
Vampire
changed the title
Ability to set a min language version for a toolchain (maybe also max)
Ability to set a min language version for a toolchain (maybe also max and preferred)
Mar 13, 2024
I have a library where I still maintain Java 8 compatibility.
But I want JavaDoc to always be created with at least Java 9 to get the nice search box.
So I could configure a Java 9 toolchain for the JavaDoc task of course.
But if someone builds with Java 11, there is not really a need to discover or auto-provision a Java 9 toolchain.
Because of that it would be nice if you could specify a toolchain with min language version (maybe there are also use-cases for max language version), so that the current toolchain is used if it is recent enough and just another one is searched if it is too old.
Currently you would probably have to do something like
The text was updated successfully, but these errors were encountered: