palantir / palantir/go-java-launcher
Incorrect absolutization of classpath argument
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 76
- Forks
- 29
- Avg merge
- 11h 34m
- Merged PRs (30d)
- 25
Description
The absolutizeClasspathEntries method here...
...doesn't seem to take into account if the classpath is already in absolute format.
I think the absolutizeClasspathEntries should check if the entry starts with a / and if so, don't prepend the working directory.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in launchlib/launcher.go at the absolutizeClasspathEntries method around line 189. Check how it handles classpath entries that are already absolute, then verify that absolute entries remain unchanged while relative entries still use the working directory; the issue does not name a test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100