Since spotless-maven-plugin 3.5.0, every execution triggers a full transitive resolution of the project's runtime dependencies — even when no formatter step needs it. In our projects the dependency graph contains a Maven version range, see Mongock's <spring-boot.version>[2.0.0, 3.0.0)</spring-boot.version>. Maven then downloads metadata and POMs for every matching version. In this case hundreds of Spring Boot POMs are fetched on every build, adding 10+ minutes to clean builds.
I think this behaviour has been introduced by the following feature: #2930 and I created a demo repo to reproduce this issue: https://github.com/sbknch/spotless-mongock-demo.
Replacing the spotless version with 3.4.0 works like a charm.
Thanks a lot for having a look, kind regards :)
Since spotless-maven-plugin 3.5.0, every execution triggers a full transitive resolution of the project's runtime dependencies — even when no formatter step needs it. In our projects the dependency graph contains a Maven version range, see Mongock's <spring-boot.version>[2.0.0, 3.0.0)</spring-boot.version>. Maven then downloads metadata and POMs for every matching version. In this case hundreds of Spring Boot POMs are fetched on every build, adding 10+ minutes to clean builds.
I think this behaviour has been introduced by the following feature: #2930 and I created a demo repo to reproduce this issue: https://github.com/sbknch/spotless-mongock-demo.
Replacing the spotless version with 3.4.0 works like a charm.
Thanks a lot for having a look, kind regards :)