You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
spring-boot/spring-boot-samples/spring-boot-sample-actuator
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
11 years ago
..
src Remove long package names from samples 11 years ago
README.md Add build.gradle samples and rename runJar->bootRun 11 years ago
build.gradle Add support for reloading resources in Gradle plugin 11 years ago
build.xml Add basic build.xml to actuator sample 11 years ago
ivy.xml Add basic build.xml to actuator sample 11 years ago
ivysettings.xml Add basic build.xml to actuator sample 11 years ago
pom.xml Add log4j starter and some documentation 11 years ago
start.groovy Ops -> Actuator 11 years ago

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.