Use the latest version in gradle-plugin as default
See original GitHub issueThis is a follow-up to my comment over here. Using version M12.3, for
/**
* Operating-System-specific utility functions.
*/
object OS {
private val OS_NAME = System.getProperty("os.name").toLowerCase()
val isWindows = OS_NAME.contains("windows")
}
I get a
NoDocOverPublicClass - [OS] at src\main\kotlin\Utils.kt:15:1
false positive (on both Windows and Linux). Interestingly, the reported line 15 is the line containing /**
, not the line containing object OS {
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
Using Gradle Plugins
By default, the plugins {} DSL resolves plugins from the public Gradle Plugin Portal. Many build authors would also like to resolve plugins...
Read more >Android Gradle plugin release notes - Android Developers
You can specify the Gradle version in either the File > Project Structure > Project menu in Android Studio, or update your Gradle...
Read more >What the difference in applying gradle plugin - Stack Overflow
The plugins block is the newer method of applying plugins, and they must be available in the Gradle plugin repository. The apply approach...
Read more >5. Add Gradle Plugin with Dependencies - Spring Cloud
To add a Gradle plugin with dependencies, you can use code similar to the following: Plugin DSL GA versions. // build.gradle plugins {...
Read more >gradle-pitest-plugin: Gradle plugin for PIT Mutation Testing
Every gradle-pitest-plugin version by default uses a predefined PIT version. Usually this a the latest released version of PIT available at the time...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
True. So let’s leave things as they are for now. After all it’s better to be explicit (by specifying the desired version of the backend in the plugin closure) than implicit (huh, what version is going to be used, esp. once the plugin and backend versions might start to mismatch).
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related topics.