Better Gradle support out on our quest out of beta

[maxandersen]

Description

There are some corner cases while using Gradle quarkus tooling or the gradle file is not behaving well.

This issue is to collect the known "bigger" issues for info.

related:
#4905 (comment)
update documentation to have both maven and gradle variation

Definition of move Gradle out of beta (2020-05-20)
Good parts:

• we have tests
• classloader isolated
  Needed:
• be a good gradle citizen (in/output)
• devmode on run from ide
• deployment/runtime mismatch (affects gradle more than maven)

Epic items

(this section is auto-generated - manual edits will get lost)

• #3552 [gradle] gradle test still not work
• #4960 Building with Gradle gives a warning about CDI dependencies
• #4982 Do not require Gradle to be installed to generate the Gradle wrapper
• #5204 Gradle plugin does not work with plugins DSL
• #5488 EntityManager in not injected when using devmode with gradle
• #5722 Gradle plugin doesn't support multi module project well.
• #6035 Pass Kotlin compiler plugin options to dev mode in Gradle
• #9046 Improve gradle and maven test harness to give us more release confidence
• #9281 Gradle build cache is not being leveraged

[gastaldi]

Here is a Gradle project using the minimum configuration (which should be generated by our tools): https://github.com/gastaldi/gradle-quarkus-project

[4ntoine]

It would be great to have Maven/Gradle switch for configuration too as current it's Maven-only.

[maxandersen]

@4ntoine can you elaborate a bit on what you are looking for ?

[4ntoine]

@maxandersen Sure, i'd like to have a switcher maven/gradle(groove/kotlin) in build configuration files, like follows (see my link):

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-bom</artifactId>
            <version>${quarkus.version}</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

<build>
    <plugins>
        <plugin>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-maven-plugin</artifactId>
            <version>${quarkus.version}</version>
            <executions>
                <execution>
                    <goals>
                        <goal>build</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

in most cases the transition is pretty straight-forward, like:

<dependency>
        <groupId>io.quarkus</groupId>
        <artifactId>quarkus-resteasy</artifactId>
    </dependency>

can be achieved with Gradle's:

implementation("...") // Kotlin DSL

However there can be more complicated usage examples.

It just removes the barriers for the newcomers (especially from Android world who mostly use Gradle as build tool).

[maxandersen]

ah you mean you don't like the use of enforced-platform/bom in our gradle file, but prefer the quarkus plugin to do the scaffolding ?

Yes, that is something I want too - just trying to figure out how we do it best reusing the dep set from the bom's the best way.

[4ntoine]

@maxandersen Sorry for being not clear enough. I've meant "provide configuration with Gradle everywhere where you can see configuration with Maven in guides now".

[maxandersen]

aaaaah! have our documentation include both maven and gradle snippets for needed config. Gotcha!

And I fully agree- I would prefer we get the actual gradle configuration simplified before go update all the docs - but yes, agreed.