TODO list:

• maven compiler plugin overrides

• release plugin? what does it do? Check with mbiarnes

• Use kogito-drools

• Import quarkus-bom to minimize our dependency version list // NO, don't do that, the quarkus-bom isn't a user bom.

• Upgrade all our dependencies. (hibernate, ...)

• Clean up dependencies: use jakarta.*
  no org.jboss.spec, javax.*

• Get rid of narayana-jta?
  • Requirements for optaplanner:
    • test with a transaction
    • test the jta of quarkus/hibernate implementation if there is any
  • Non-reqs: test with distributed transaction

• Get rid of yasson?

• Get rid of moxy?

• sonarcloud profiles

• namespace properties by maven plugin

• Remove spotbugs. Keep Sonarcloud
  Sonar won't fail the build VS build time => lesser evil is build time
  Sonar should fail the CI build for very critical issues

• Clean up jacoco

• Clean up checkstyle - merge configuration
  remove properties and hard code them

• do we want to keep checkstyle?
  Why (not)? build speed cost
  Check what it does more than the formatter.
  What about Sonar - can it take over those responsibilities and fail?
  Maybe not.
  When is the last time you saw checkstyle fail? I can't remember
  => Maybe we don't need it: between the formatter and sonarcloud
  we're safe.
  => What are the checks we can not live without?

• revapi-oldKieVersion -> old (optaplanner) version?

• enforcer: ban org.jboss.spec.* and javax.*

• move javoco config into profile