typetools / typetools/checker-framework
-classpath argument only works on command line, not in an argfile
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
What steps will reproduce the problem?
1. Run:
java -jar checkers.jar -classpath path/to/customChecker.jar -processor
path.to.CustomChecker <src files>
Everything should work via this invocation
2. Write classpath to a file like @myclasspaths.txt The file should have a
single line like:
-classpath path/to/customChecker.jar
3. Run:
java -jar checkers.jar @myclasspaths.txt -processor path.to.CustomChecker <src
files>
This invocation leads to an error message that indicates BaseTypeChecker is
missing. Putting checkers.jar in @myclasspaths.txt fixes this (which is
currently what the Eclipse/Maven plugins do).
We should never have to put checkers.jar on the classpath manually when running
checkers.jar.
Original issue reported on code.google.com by Jonathan...@gmail.com on 7 Jan 2013 at 3:36
Contributor guide
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
Reproduce the two commands using checkers.jar and the @myclasspaths.txt argfile described in the issue, then trace the command-line entry point that expands argfiles and resolves the classpath. Done means the argfile invocation finds BaseTypeChecker without requiring checkers.jar to be listed in the file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100