Make gradle plugin available for easy/conventional gradle usage

[maxandersen]

Today we need a lot of scaffolding in users gradle setup:

plugins {
    id 'java'
}

apply plugin: 'io.quarkus'

pluginManagement {
    repositories {
        mavenCentral()
        gradlePluginPortal()
    }
    resolutionStrategy {
        eachPlugin {
            if (requested.id.id == 'io.quarkus') {
                useModule("io.quarkus:quarkus-gradle-plugin:${requested.version}")
            }
        }
    }
}

where if we published to gradle registry users would just need this:

plugins {
    id 'java'
    id 'io.quarkus'
}

for now it is assumed we must make the gradle plugin an actual gradle project to make this happen - need to verify that

[geoand]

I think the gradle plugin does indeed need to be a gradle project, if not for any other reason than the fact that the necessary build tool plugins that would allow publishing to the Gradle Portal only exist for gradle.

[maxandersen]

duplicate of #1793

[cniweb]

+1

[Sanne]

@maxandersen Gradle plugins can decorate other plugins; the goal should be to require users to just

plugins { id 'io.quarkus' }

(the 'java' plugin should be unnecessary - unless there's need to differentiate for the Kotlin projects but I think that could be skipped or handled as a different plugin id)

[Sanne]

example of a full build scripts - as in the POC I shared a while back with the team:

plugins { id 'io.quarkus' }

quarkus {
  version = ''
}

extensions {
  'io.quarkus.hibernate',
  'io.quarkus.resteasy',
  'io.quarkus.mariadb'
}

In other words: the full coordinates of extensions are also redundant, and the build tools could actually take advantage of this so to treat the dependencies-declares-as-extensions in a more efficient way.

Also, it makes it redundant to pick extension versions. the quarkus version block could be optional, defaulting to latest, or to the version matching the plugin version.

[gastaldi]

My user doesn't have permission to push to the portal. Since this is part of the release process, I am assigning this issue to @gsmet . The Gradle plugin is all set to be published, all that's left is the API key and secret with permission to publish the io.quarkus plugin. See #1793 (comment)