Add 'latest' as alias for version 'x'#53
Conversation
While it is possible to specify that you want the latest JDK version by using semver X-Ranges (like 'x' for example), 'latest' is more readable as explicitly states the intention.
|
To be honest I'm not quite sure if the tools cache plays well with |
Since the semver version parsing is done directly on the CDN contents, the caching (outside of the CDN itself) is not a significant issue. My experience has been that things we put in the CDN show up in .x version results fairly quickly (the longest I've seen had been about 30 minutes). |
|
+1 for this. It took me a while to understand what it is for (since x technically works), but since the string we use to specify the version in a matrix is then typically used in the job name, I agree that seeing "Java latest" as a job name is much more readable than "Java x". |
|
Actually I did some tests. If 'x' is specified the version in the tools cache is used. But if 'latest' is specified the version in tools cache is not found as |
|
Yes, it does not work for 1.8 as well. I'll open an issue and provide PR. |
|
Hello @plamentotev , if it is still actual for you - we don't have objections to accept this PR. |
|
I think I found a better way to achieve the same so I'll close it. |
3 participants
With the new release cycle a new JDK version is released once every six months. It may not seems like that often, but still adds overhead to update the build matrix with the latest JDK version. It is more convenient to set the build to run on the LTS versions that the project supports plus the latest JDK version. I've created a proof of concept workflow [1].
While it is possible to specify that you want the latest JDK version by using semver X-Ranges (like 'x' for example), 'latest' is more readable as explicitly states the intention. Also if you use the value from the build matrix in your job name, "JDK:latest" is better than "JDK:x".
[1] The workflow uses my change as asked by the contributors guide