Implicitly import `java` flag for `kotlin` and `scala` flags
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 80
- Forks
- 34
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 1
Description
`kotlin` and `scala` flags are added for configuring the default settings for Kotlin and Scala.
However, they can not activate the common features enabled by `java` such as publishing, relocation, coverage, and so on.
Even though the `kotlin` flag is set to a pure Kotlin project, it also needs a `java` flag.
Otherwise, the project will not be configured or executed as expected.
I think we can assume `kotlin` and `scala` is a superset of `java` flag. So it is convenient to implicitly import `java` flag for them.
```diff
- // Before
- includeWithFlags ':my-kotlin-project', 'java', 'publish', 'relocate', 'kotlin'
+ // After
+ includeWithFlags ':my-kotlin-project', 'kotlin', publish', 'relocate'
```
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
Locate the implementation of the `java`, `kotlin`, and `scala` flags and inspect how `includeWithFlags` applies shared defaults. Verify whether Kotlin and Scala projects can inherit Java features such as publishing, relocation, and coverage without explicitly listing `java`. Done means the example no longer needs the `java` flag while those common features remain enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, scala
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100