Skip to content

Conversation

@Okeanos
Copy link
Contributor

@Okeanos Okeanos commented Aug 20, 2025

Add additional locations for auto-discovery to scan

Resolves #129


Since 3f9736c running tests locally (on macOS) fails the build; I have not yet had the chance to debug this fully and understand whether it's a setup problem on my machine.


Following this checklist to help us incorporate your
contribution quickly and easily:

  • Your pull request should address just one issue, without pulling in other changes.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body.
    Note that commits might be squashed by a maintainer on merge.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
    This may not always be possible but is a best-practice.
  • Run mvn verify to make sure basic checks pass.
    A more thorough check will be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@laeubi laeubi requested a review from gnodet November 13, 2025 04:27
@laeubi
Copy link

laeubi commented Nov 13, 2025

@gnodet can you take a look?

} else {
installedDirs.add(Paths.get("/usr/jdk"));
installedDirs.add(Paths.get("/usr/java"));
installedDirs.add(Paths.get("/usr/local/java"));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which tool uses this directory ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is based on the proposed alignment with the Gradle toolchain detection I mentioned in #129 – the original proposal for Gradle is documented in gradle/gradle#23620 and boils down to "people put it there during manual installations as common default".

I have no strong opinion on this and I am willing to exclude this particular search folder as it is a "customary" but ultimately a user-defined location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include additional scan locations for auto discovery

3 participants