v5.0.1 release notes
- Implemented partial workaround for GH-596 where users may experience OutOfMemoryExceptions being raised by Eclipse Aether during dependency resolution. - The plugin now follows similar behaviour to Maven Core by not recursing into transitive test dependencies and fat artifact dependencies, which was considered to be surprising and undefined behaviour.
- Users depending on the old behaviour should explicitly declare their dependencies following standard Maven conventions.
- This is not deemed a breaking change since the old behaviour is undefined and does not follow Maven default behaviour.
- Reverted offloading project dependency resolution to Maven to address GH-939.
- This previously manifested as various Maven reactor failures when resolving sibling dependencies in a Maven multi-module project.
- Users can now disable dependency resolution for the main project dependencies correctly by setting
<ignoreProjectDependencies>true</ignoreProjectDependencies>and only specify their protobuf dependencies via the plugin itself.
- Reduced default concurrency multiplier used for various internal tasks after several JFR profiling sessions showed a general lack of utilisation of the thread pool.
- This should reduce idle resources slightly in builds.
- Various Aether internals are now cached for the duration of the plugin goal rather than recreated numerous times during dependency resolution.
- This should reduce resource usage slightly in builds.
- Updated plugin to use
protobuf-java:4.34.0for various descriptor file-related activities. - Updated project and integration test dependencies to verify plugin compatibility across various component matrices.