Skip to content
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

Run Gradle plugin extensions #2411

Merged
merged 1 commit into from
Apr 16, 2020

Conversation

chanseokoh
Copy link
Member

Gradle counterpart of #2397.

Using the standard Service Provider Interfaces (SPI) mechanism to load and run Gradle plugin extensions.

This doesn't yet involve the new extension config option (like jib.extensions=[ { implementation='com.example.ExtensionClass' }]). The config option can be added in a later PR.

With this, we are actually enabling running and testing Gradle extensions. Extensions should be added to the classpath of the Gradle build script. Extensions added in this way apply to all sub-modules in a multi-module project, so we do need the new config option in the end.

buildscript {
    dependencies {
        classpath 'com.google.cloud.tools.jib.plugins.extension.gradle.quarkus:quarkus-extension-gradle:0.1.0-SNAPSHOT'
    }
}

@chanseokoh chanseokoh merged commit 0d8874f into master Apr 16, 2020
@chanseokoh chanseokoh deleted the gradle-plugin-extension-run-extensions branch April 16, 2020 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants