-
Notifications
You must be signed in to change notification settings - Fork 61
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
Publish Gradle plugin to https://plugins.gradle.org #56
Comments
when would we published to the Gradle Plugin Portal? I'd really like the simplified |
add this to your setting.gradle(.kts) pluginManagement {
repositories {
gradlePluginPortal()
}
resolutionStrategy {
eachPlugin {
val module = when(requested.id.id) {
"kotlinx-atomicfu" -> "org.jetbrains.kotlinx:atomicfu-gradle-plugin:${requested.version}"
else -> null
}
if(module != null) {
useModule(module)
}
}
}
} it can bridge it .. but having it published properly as a gradle plugin would make this easier to use and integrate better with version management plguins like https://docs.gradle.org/current/userguide/publishing_gradle_plugins.html |
@NikkyAI do we still need to do it? I've just added the plugin via
and everything seems to work, although I cannot find the UPDATE It works if I add the plugin to the subproject, but fails if I do it in the top level |
well this is what we needed.. https://plugins.gradle.org/plugin/org.jetbrains.kotlin.plugin.atomicfu maybe update the README to show how to apply the plugin ? then this issue can be closed as far as i am concerned... |
Any potential error or naming with the new not-in-readme plugin? Trying to use the plugin dsl
The plugin resolved but
would have a When I switch back to the
The |
It seems |
I am applying it in my id 'org.jetbrains.kotlin.plugin.atomicfu' version '1.9.22' apply false And when I apply it in a non-root project:
nothing at all happens so far as I can tell. |
Gradle plugin repository https://plugins.gradle.org allows using the new plugin DSL in Gradle without any additional configuration, e.g.
Right now we may only use the older
buildscript{..}
approachThe text was updated successfully, but these errors were encountered: