There is no written convention. Personally I prefer gradle-XXX-plugin, to (hopefully) make it clear that it's a plugin for Gradle.
Gradle plugin naming convention
Question
Is there an unwritten convention (or a written one, I didn't find) how a Gradle plugin for technology XXX would be called? Examples for the two obvious possibilities:
- XXX-gradle-plugin: license-gradle-plugin
- gradle-XXX-plugin: gradle-cargo-plugin
I think there are good reasons for both naming conventions. In the Maven community the naming XXX-maven-plugin is recommended, so I currently tend to use this one. Am I missing something?
La solution
Licencié sous: CC-BY-SA avec attribution
Non affilié à StackOverflow