swiftlang / swiftlang/swift-java
Add CI job that checks/regenerates JavaStdlib etc with wrap-java
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
We always want the "latest" version of those generated sources.
swift-java wrap-java generated sources inside SwiftJava and JavaStdlib should always be up to date.
if running a wrap run on a new commit changes the sources, we changed the wrap-java logic and we should audit that and/or regenerate the sources.
The CI job should make sure we don't regress features this way and that we always have the latest version of generated sources.
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 by reviewing the existing CI configuration and the generated sources inside SwiftJava and JavaStdlib. Run wrap-java on a new commit and compare the generated sources; the work is done when CI detects any differences and indicates that wrap-java logic should be audited or the sources regenerated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, swift
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100