I've added support for the CLASSPATH environment variable in InferCon… #323
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…fig.
This change modifies the
InferConfig
class to allow the Java language server to determine the project's classpath using theCLASSPATH
environment variable.Key changes:
classPath()
method inInferConfig.java
now checks for theCLASSPATH
environment variable first. If set, its value is parsed and used as the classpath. This allows you to override the default classpath discovery mechanisms (Maven, Bazel).InferConfig.java
was refactored to allow injection of environment variables for testing purposes. This involved adding a new constructor that accepts a map of environment variables and updating methods that access environment variables to use this injected map.classpathFromEnvironmentVariable
, was added toInferConfigTest.java
to specifically verify the new functionality. This test uses the new constructor to inject a mockCLASSPATH
variable.All tests in
InferConfigTest.java
, including the new test, pass.Note: During testing, I observed three pre-existing test failures in other classes (
CompletionsTest.overloadedOnClassPath
,FindSrcZipTest.testFindSrcZip
,HoverTest.docString
). These failures are believed to be unrelated to the changes in this commit and should be investigated separately.