Java teams struggle to share flexible project JDK requirements
Java developers want a project to specify acceptable JDK versions, but an exact patch-version or distribution pin can fail when collaborators have a different compatible JDK installed. Switching JDKs between projects can also mean manually changing JAVA_HOME, while the cited SDKMAN requests seek ways to choose among acceptable installed versions. A migration-guide complaint appears in the evidence too, but is separate from this version-selection problem.
For java developers and teams. Mentioned from Mar 2020 to Nov 2025 on GitHub and Hacker News.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 4.8/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I can commit a file with java=17.0.2-tem but then that will fail for a user who only has 17.0.1-tem or a different java 17 distro
SDKman: here are the versions of Java that are considered acceptable for use. The first one you find, use that one. If none is loaded, then tell the user that they need to install one of the following list:
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks