Gradle plugins are usable with plugins {...} syntax if they have plugin markers
Currently app-gradle-plugin does not publish one, so the users struggle.
It would be great if the markers were published.
Currently, app-gradle-plugin uses maven to publish to Nexus. maven is deprecated for a long time, and it is probably time to migrate to maven-publish
I don't know the way you publish/release, and I don't want to interrupt workflows, however, I guess the following might be a sane plan:
- Bump Gradle (e.g. to 6.8.2)
- Use
maven-publish for publishing
- Use Gradle's
java-gradle-plugin for plugin marker generation
- Use https://github.com/gradle-nexus/publish-plugin for Nexus staging. Just in case, staging enables you to create a "staging" repository, push multiple artifacts and release them at once (or drop the staged repo)
- Use Kotlin DSL for Gradle for less magic and better autocomplete
WDYT?
Gradle plugins are usable with
plugins {...}syntax if they have plugin markersCurrently
app-gradle-plugindoes not publish one, so the users struggle.It would be great if the markers were published.
Currently,
app-gradle-pluginuses maven to publish to Nexus.mavenis deprecated for a long time, and it is probably time to migrate to maven-publishI don't know the way you publish/release, and I don't want to interrupt workflows, however, I guess the following might be a sane plan:
maven-publishfor publishingjava-gradle-pluginfor plugin marker generationWDYT?