This message was deleted.
# plugin-development
s
This message was deleted.
l
This is expected to be the last RC before GA, so please test it out.
j
Is there a migration guide from the last non 1.0.0 version?
l
Not really because the previous versions actually supported multiple ways of doing things, each of them having their own specifics. The new approach is: • Make it work with
maven-publish
and
java-gradle-plugin
(applied by
kotlin-dsl
) • Then applying
plugin-publish
is just to enable portal publication. See the docs for some of the things it helps simplify
The upcoming updated doc can be useful as well: https://docs.gradle.org/nightly/userguide/publishing_gradle_plugins.html
j
Hey @Louis Jacomet, I am applying the signing plugin but I am not configuring it for snapshot versions, with the normal publication I have no issues, but with the plugin one I am getting that I haven’t configured the signature, the only solution is applying the plugin conditionally?
l
The pattern we see most often is that the plugin is always configured but signing is disabled in some cases. See https://docs.gradle.org/current/userguide/signing_plugin.html#sec:conditional_signing If you follow this, then it should work. If not, please open an issue and share a reproducer on https://github.com/gradle/plugin-portal-requests/issues
👍 1
j
My current use case is with all publish tasks, so hasTask is not valid, and allTasks is empty, is it safe to config the signing when taskGraph is ready?
Looks like it is not safe