swiftlang / swiftlang/swift-java
swift-java configure should not write classpath to swift-java.config
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
Since those end up being local filesystem paths.
We must instead just rely on the swift-java.classpath files in the configure command as well as in wrap-java
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
Start at the configure and wrap-java command implementations, then inspect how swift-java.config and swift-java.classpath are read and written. Confirm the behavior for local filesystem paths and verify that both commands rely on the classpath files without writing those paths to swift-java.config.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100