Closed jerzykrlkroche closed 1 year ago
I think you can workaround this issue by setting the spring dependency directly in settings.gradle
. You must set it as a classpath dependency.
The proper fix would be to update the dependency in the license plugin, likely triggering a 0.17.0
release.
Kordamp plugin suite won’t work well with a recent Spring Boot Gradle plugin.
Kordamp seems to be indirectly including an ancient Spring version, like this:
This seems a bit tricky to fix, because there’s a new
com.mycila:license-maven-plugin:4.2.rc3
, which doesn’t depend on Spring libs any more. But thegradle.plugin.com.hierynomus.gradle.plugins:license-gradle-plugin:0.16.1
is the most recent version available.I don't have a good idea, what'd be the right place to put the fix - any thoughts?