Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-3346

Migrate from Gradle to Maven

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • 2025-07-08 - API
    • None
    • None
    • maven migration
    • False
    • Hide

      None

      Show
      None
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done

      Gradle brings the following disadvantages that makes our day to day harder in a developer viewpoint perspective:

      • Poor Quarkus integration

      This is not really an issue with Gradle, but with Quarkus. However, if we're committed to keep using Quarkus, this is a pain. Example of issues: (1) random failures when building in parallel; (2) using Gradle daemons for builds

      • Hard to troubleshoot build/test failures

      Need to scroll up to spot what the failures are.

      • Need Intellij Ultimate to work

      We can't easily use our project with Intellij Community Edition. Maven is supported instead.

      • Using an old version of Gradle 8.5. I can't upgrade to Gradle 8.12 (latest) because it can't detect Java JDK in Linux.

      Have had issues trying to use VS Code with gradle because of the annotation processing that the internet says hasn't been an issue with maven

              Unassigned Unassigned
              jcarvaja@redhat.com Jose Carvajal Hilario
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: