Somehow this plugin is excluding junit

[wgorder]

To Reproduce:

go to start.spring.io create a new groovy/gradle/java 1.8 project with web, security, and actuator.

Alter the build.gradle to use the dependency management:

buildscript {
    ext {
        springBootVersion = '1.2.0.RELEASE'
    }
    repositories {
        mavenCentral()
    }
  dependencies {
    classpath("org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}")
    classpath 'io.spring.gradle:dependency-management-plugin:0.3.0.RELEASE'
  }
}

apply plugin: 'groovy'
apply plugin: 'eclipse'
apply plugin: 'idea'
apply plugin: 'spring-boot'
apply plugin: 'io.spring.dependency-management'

jar {
    baseName = 'my-appi'
    version = '0.0.1-SNAPSHOT'
}
sourceCompatibility = 1.8
targetCompatibility = 1.8

repositories {
    mavenCentral()
}

dependencyManagement {
  imports {
    mavenBom "org.springframework.boot:spring-boot-versions:${springBootVersion}"
  }
}

dependencies {
    compile("org.springframework.boot:spring-boot-starter-security")
    compile("org.springframework.boot:spring-boot-starter-web")
    compile("org.springframework.boot:spring-boot-starter-actuator")
    compile("org.codehaus.groovy:groovy")
    testCompile("org.springframework.boot:spring-boot-starter-test")
}

eclipse {
    classpath {
         containers.remove('org.eclipse.jdt.launching.JRE_CONTAINER')
         containers 'org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8'
    }
}

task wrapper(type: Wrapper) {
    gradleVersion = '1.12'
}

The test will fail because of a missing junit dependency:
running gradle dependencies will show that indeed for whatever reason that one dependency is excluded.

Remove the dependency plugin and it works again.

[wilkinsona]

Looks like a bug in 0.3.0 that aims to honour Maven exclusions. You may want to try 0.2.1 until a fix is available. Alternatively, declaring a direct dependency on JUnit should also work.

[wgorder]

Unfortunately the direct dependency on junit does not work. I had tried that first :)

[wilkinsona]

Sorry about that. I'm intrigued now. There's a test that verifies that a direct dependency prevents an exclusion.

As an aside, and it won't help with this problem, you should use spring-boot-dependencies rather than spring-boot-versions.

[wgorder]

I was wondering about that. I used the same convention as spring-cloud, although I noticed all spring boot does is pull in the dependencies pom anyway. I have no idea how that test passes based on what I saw, seems like a mystery.

[wgorder]

Here is another weird one. With 0.3.0 this worked

dependencyManagement {
  imports {
    mavenBom "org.springframework.boot:spring-boot-dependencies:${springBootVersion}"
  }
}

but on 0.2.1 you have to do this

dependencyManagement {
  imports {
    mavenBom "org.springframework.boot:spring-boot-dependencies:1.2.0.RELEASE"
  }
}

or you get the error

 No such field: springBootVersion for class: io.spring.gradle.dependencymanagement.DependencyManagementHandler

[wgorder]

Nvm :)
#17

[wilkinsona]

This should now be fixed in 0.3.1.BUILD-SNAPSHOT which is available from https://repo.spring.io/plugins-snapshot. It'd much appreciated if you could give it a quick test and confirm that it's now working for you too. I might just manage to squeeze in a 0.3.1 release before Christmas.

[wgorder]

Its working for me. Nice work!

[wilkinsona]

Excellent. Thanks for testing it.