-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unlock plugins {...} syntax: publish plugin markers to Sonatype OSSRH (Maven Central) #1004
Comments
Sorry, we're always a little slow during the weekends. So we actually have a special release process where we sign with the google open source key (which must be done out of the standard build process). So we do not publish directly using the maven (or maven-publish), |
Long story short: I want to migrate my Python-Google App Engine-based app to Kotlin. The samples are there, however, it turns out they are out of date :(. I thought I could reduce the friction, so I created a PR to refresh kotlin-samples and a PR to refresh app-gradle-plugin Of course, now I got the sample working. I hope the publication of the plugin markers and updating the samples would ease the learning curve and it won't disrupt your workflows much. /cc @jamesward |
Thanks for the heads up. I've just been working on the Cloud Run Kotlin samples not the App Engine ones. Sorry I'm not more helpful on this. |
Workaround in pluginManagement {
resolutionStrategy {
eachPlugin {
if (requested.id.id == "com.google.cloud.tools.appengine") {
useModule("com.google.cloud.tools:appengine-gradle-plugin:${requested.version}")
}
}
}
} |
Gradle plugins are usable with
plugins {...}
syntax if they have plugin markersCurrently
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-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-publish
for publishingjava-gradle-plugin
for plugin marker generationWDYT?
The text was updated successfully, but these errors were encountered: