spring-boot/spring-boot-integration-tests/spring-boot-gradle-tests/src/test/resources/boot-run-resources/build.gradle

buildscript {
	repositories {
		mavenLocal()
	}
	dependencies {
		classpath("org.springframework.boot:spring-boot-gradle-plugin:${project.bootVersion}")
	}
}

apply plugin: 'java'
apply plugin: 'spring-boot'

repositories {
	mavenLocal()
}

bootRun {
	addResources = Boolean.valueOf(project.addResources)
}
Add support to the Gradle plugin for disabling direct use of resources The Maven plugin allows spring-boot:run to be configured so that resources are loaded from their output location rather than from src/main/resources. This commit adds an equivalent configuration option to the Gradle plugin. To disable source resources from being added to the classpath in place of those in the output location the configure the bootRun tasks like this: bootRun { addResources = false } Closes gh-2431 2015-02-03 18:48:21 +08:00			`buildscript {`
			`repositories {`
			`mavenLocal()`
			`}`
			`dependencies {`
			`classpath("org.springframework.boot:spring-boot-gradle-plugin:${project.bootVersion}")`
			`}`
			`}`

			`apply plugin: 'java'`
Revert "Upgrade Gradle plugin’s ID so it’s suitable for the Plugin Portal" This reverts commit b1c0a7cda486e4f745b4233715efb8c0dc2814df. The plugin publishing process has moved to a new plugin-based approach that brings with it some significant limitations: - There's no staging to allow the promotion of good release builds - There's no easy way to upload an existing artifact - There's no control over the published pom. The risk brought by these limitations, particularly the first, are too great so we will no be publishing the Boot plugin to the Portal until they're resolved. Changing the plugin's ID was a breaking change that would require users to do some work when they upgrade to Boot 1.3. The ID of the plugin was changed purely so that it met the Portal's requirements. Given that the plugin will not be published to the Portal for the foreseaable future there's no need for us to inflict a breaking change on people when there will be no benefit. See gh-1567 2015-04-20 20:51:44 +08:00			`apply plugin: 'spring-boot'`
Add support to the Gradle plugin for disabling direct use of resources The Maven plugin allows spring-boot:run to be configured so that resources are loaded from their output location rather than from src/main/resources. This commit adds an equivalent configuration option to the Gradle plugin. To disable source resources from being added to the classpath in place of those in the output location the configure the bootRun tasks like this: bootRun { addResources = false } Closes gh-2431 2015-02-03 18:48:21 +08:00
Replace basic Gradle dependency management with use of separate plugin This commit replaces Spring Boot's basic dependency management support with separate dependency management plugin. This has a number of benefits including: 1. A Maven bom can be used rather than a custom properties file 2. Dependency management is applied transitively rather than only to direct dependencies 3. Exclusions are applied as they would be in Maven 4. Gradle-generated poms are automatically configured with the appropriate dependency management Closes gh-2133 2015-03-19 01:08:07 +08:00			`repositories {`
			`mavenLocal()`
			`}`

Add support to the Gradle plugin for disabling direct use of resources The Maven plugin allows spring-boot:run to be configured so that resources are loaded from their output location rather than from src/main/resources. This commit adds an equivalent configuration option to the Gradle plugin. To disable source resources from being added to the classpath in place of those in the output location the configure the bootRun tasks like this: bootRun { addResources = false } Closes gh-2431 2015-02-03 18:48:21 +08:00			`bootRun {`
			`addResources = Boolean.valueOf(project.addResources)`
			`}`