Hello,
Thank you very much for the thoughtful feedback — this is extremely helpful.
You are absolutely right that JDT already provides strong mechanisms for JDK discovery and configuration, and that tools like SDKMAN as well as plugins such as JRE Discovery already address parts of this space. I certainly do not want to duplicate existing functionality or replace system-level JDK managers.
Based on this discussion, I see the idea evolving into something more focused and complementary rather than overlapping. The potential differentiator would be:
- Direct integration with the official Adoptium API for version discovery
- Clear visibility of LTS vs non-LTS releases
- Awareness of Adoptium-specific release cadence
- A streamlined in-IDE download and registration flow using existing JDT mechanisms
- Optional security/update awareness for installed Temurin JDKs
In other words, not a general-purpose JDK manager, but a lightweight Adoptium-aware assistant that builds on JDT’s existing capabilities rather than replacing them.
If that still appears redundant given current tools, I would greatly appreciate guidance on whether narrowing the scope further (for example to preference-based integration only) would make more sense.
Thank you again for the valuable input.
Best regards,
Daksh Sharma