Konrad Windszus
Konrad Windszus
This is a bug in Java (https://bugs.openjdk.org/browse/JDK-8335181). Meanwhile fixed 24, and newer 17 and 21 versions.
@cstamas Is DOMTrip ready for using it inside m-release?
Java 17 is fully supported in plugins/extensions since 3.9.6: https://github.com/apache/maven/issues/8732
I still don’t see why > This would make Maven Release unusable with Maven 3 because it requires Java 17. As said before Java 17 plugins work fine in Maven...
Right, but the question is why you consider this incompatible with Maven 3….
You said > This would make Maven Release unusable with Maven 3 I beg to differ
For example #1304 or #1274
Unfortunately there doesn't seem to be a clear distinction. Most methods from `ScmManager` are just shortcuts to same named methods of the provider of the given repo, but the provider...
Blocked by https://github.com/eclipse-jgit/jgit/issues/193
> can you resolve the conflicts? Only once I have someone's confirmation that this is something we can/should do in a minor version upgrade.