version a file to capture the java version for the project

[travi]

should this encourage a single approach to this for consistency, or would it be better to enable multiple options as choices?

Known Options

• SDKman
• jEnv

Considerations

• compatibility with the setup-java action
• ability to leverage renovate to prevent the version from growing stale

[travi]

renovate status:

• jenv
• sdkman (note that an issue was never opened)

[travi]

possibly also worth considering asdf, which renovate does support

[travi]

sdkman is not supported natively by setup-java, but there is a community supported action

[travi]

it looks like the intention of the setup-java action is to only ever support the .java-version file (used by jenv)

[travi]

https://github.com/marketplace/actions/java-info-action supports jenv and asdf approaches

GitHub

Java Info Action - GitHub Marketplace

Fast Maven/Gradle parser detects and extracts info such as Java version, project version, encoding, build cmd and props