Application plugin configuration seems unnecessary on Gradle 4.8
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 48
- Forks
- 36
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 8
Description
@DJViking commented on Tue Jun 19 2018
The application plugin run configuration seems unnecessary.
https://guides.gradle.org/building-java-9-modules/#modify_the_code_run_code_task_to_use_modules
It works fine without both run{} and startScripts{} configurations running Gradle 4.8 on JDK 10.
Could it be changed from Gradle 4.7 which the Guide was targeted for?
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 with the “Modify the run task to use modules” section of the linked Java 9 modules guide and compare its run{} and startScripts{} configuration with Gradle 4.8 on JDK 10. Done means the guide accurately reflects whether those configurations are needed for the supported Gradle and JDK versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100