Bails out with the following stack trace at “apply plugin: ‘spring-boot’” with spring-boot 1.3.5.
My two other projects that aren’t using the above plugin work fine.
Bails out with the following stack trace at “apply plugin: ‘spring-boot’” with spring-boot 1.3.5.
My two other projects that aren’t using the above plugin work fine.
spring-boot projects work OK for me when I’m using a current snapshot of the dependency-management-plugin. I guess the issue will probably not be fixed by a future version of gradle-3.0. You’ll have to use the upcoming version 0.6.0 of the plugin. See GRADLE-3482 for details.
I use the dependency-management-plugin
transitively via 'org.springframework.boot:spring-boot-gradle-plugin:1.3.5.RELEASE'
and won’t manually override its dependencies.
I mainly wanted to ensure that this broken compatibility in what I’d consider a very critical plugin is a known issue so it gets addressed in an updated version of either Gradle 3.0, spring-boot or both.
But thanks anyway for your suggestion/workaround. Appreciated!
Minimal workaround:
buildscript {
repositories {
// [your other repos]
// below is TEMPORARY! Remove while upgrading spring-boot to 1.4.0!
maven { url "https://repo.spring.io/plugins-snapshot" }
// above is TEMPORARY! Remove while upgrading spring-boot to 1.4.0!
}
dependencies {
// [your other build dependencies]
// below is TEMPORARY! Remove while upgrading spring-boot to 1.4.0!
classpath 'io.spring.gradle:dependency-management-plugin:0.6.0.BUILD-SNAPSHOT'
// above is TEMPORARY! Remove while upgrading spring-boot to 1.4.0!
}
}
I use it transitively, too. For me, overriding the version within the build.gradle works perfectly. Now there is even a stable version of the dependeny plugin. You may take a look here.