Andres Almiray

Enforcer is to to validate the correct version of Maven is used regardless of if the wrapper is used or not.

Will take a look next week.

Well in my case Maven Local is in the default path and it didn't work either.

The actual amount is up to the given sponsor(s) but starts at USD 500 https://opencollective.com/jreleaser

Yes, keep the current name for backward compatibility but also offer the new name to start the migration. right now both artifacts will match in content. Later on they might...

This is already possible IF you use the jreleaser-maven-plugin and consume a `jreleaser.yml` file. It cannot be done if you use the jreleaser CLI. https://jreleaser.org/guide/latest/tools/jreleaser-maven.html#_defaults

If I understand correctly, artifacts are created by means other than Maven or Gradle (be it using plain JDK tools or other build tools such as sbt, leinigen, ant, bazel,...

If this is your first time using the Kordamp Gradle Plugin suite to aggregate JaCoCo reports then I'd suggest you move on and use JaCoCo directly. I believe Gradle 7...

Well, the exception occurs as long as there's no plugin that can provide `aar` packaging. Adding the following to the pom should be enough to make pomchecker work ```xml com.simpligility.maven.plugins...

Pomchecker requires building a fully resolved model from the input pom file. This means a component must be able to resolve `aar`. Gradle does not generate pom files with such...