Update get classpath by artifact name to support bazel #4750
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.
What's changed?
Added support to retrieve the classpath by artifact name for Bazel projects.
What's your motivation?
In Bazel projects, creating an instance of JavaParser with artifact names as classpath can fail when artifact names include a "-". This issue arises because Bazel replaces "-" with "_" when generating JAR files.
Example usage
Above code fails with
IllegalStateException Unable to construct JavaParser
.To address this, updated JarPattern to include the normalized artifact name, ensuring it can correctly locate the JAR file names generated using bazel convention.
Note: A minor refactor to make code testable for the part which was updated.
Checklist