[Idea/Add] get recommended Java Version from the api/v2

[LuckCrafter]

I'll like to see a feature to get the recommended Java version for PaperMC (something like in the docs)

[electronicboy]

recommended java version just seems completely irrelevant to the distribution system

[MiniDigger]

I agree with cat, but I also see the other side, the api is our main communication channel to hosts, such a feature could greatly reduce the work they have to do to deploy stuff.
maybe we can add a tagging system so we can add metadata like this to version groups?

[electronicboy]

My issue is, what constitutes as recommended? Tagging the build version is trivial, but, the notation of recommendations is somewhat iffy as we always just recommend the latest version that we know works for X a release, and am not sure that's something we should particularly be tryna maintain here

[MiniDigger]

we already maintain it on the docs, as OP said, so idk,. what do others think?

[Machine-Maker]

Why not minimum java version instead of recommended?

[e-im]

Minimum you can just get via the class file version, recommended (especially back on 1.16 and below, where recommended ≠ minimum) was harder and just involved hard coding a table. Also see PaperMC/Paper#5630 for another possible approach/more rational.

[electronicboy]

We maintain it on the docs in a place which isn't updating the metadata of several dozen builds at once? Unless you mean per release in which kills the granularity and creates some complexities when java issues are fixed or the max supported ver is bumped, etc
I just feel that a recommended version is far too nuanced for something which others will push onto others less fortunate

[MiniDigger]

I would have defined it on the version group