mirror of https://github.com/spring-projects/spring-boot.git synced 2024-09-03 04:26:12 +08:00

History

Dave Syer 5592023f16 Add support for reloading resources in Gradle plugin Usage: $ gradle bootRun ... Edit files in src/main/resources and see the changes live in a web app (e.g. static resources in /static). The old functionality of bootRun has been replaced (since it didn't add a lot of value and also didn't expose any JMV argument setters of anything). This new feature set is backed by any existing "run" task configuration. In addition autodetects a main class if there is one in the project sources, so no need for mainClassName = '...' in build.gradle. Applies the 'application' plugin (so no need to declare that either). Fixes gh-225		2014-01-15 11:26:33 +00:00
..
src	Remove long package names from samples	2013-12-31 08:40:26 +00:00
build.gradle	Add support for reloading resources in Gradle plugin	2014-01-15 11:26:33 +00:00
build.xml	Add basic build.xml to actuator sample	2013-12-23 14:50:58 +00:00
ivy.xml	Add basic build.xml to actuator sample	2013-12-23 14:50:58 +00:00
ivysettings.xml	Add basic build.xml to actuator sample	2013-12-23 14:50:58 +00:00
pom.xml	Add log4j starter and some documentation	2013-12-16 17:26:53 +00:00
README.md	Add build.gradle samples and rename runJar->bootRun	2013-12-10 11:10:04 +00:00
start.groovy	Ops -> Actuator	2013-07-31 13:20:26 -07:00

README.md

Spring Boot Actuator Sample

You can build this sample using Maven (>3) or Gradle (1.6).

With Maven:

$ mvn package
$ java -jar target/*.jar

Then access the app via a browser (or curl) on http://localhost:8080 (the user name is "user" and look at the INFO log output for the password to login).

With gradle:

$ gradle build
$ java -jar build/libs/*.jar

The gradle build contains an intentionally odd configuration to exclude the security dependencies from the executable JAR. So the app run like this behaves differently than the one run from the Maven-built JAR file. See comments in the build.gradle for details.