spring-boot/spring-boot-samples/spring-boot-sample-actuator
Dave Syer f448e79f29 Remove long package names from samples
Long package names are really unnecessary in samples and they
just clutter things up. Also Spring Loaded doesn't work with
org.sfw packages, so to demo that technology you need a
different package name.
2013-12-31 08:40:26 +00:00
..
src Remove long package names from samples 2013-12-31 08:40:26 +00:00
build.gradle Add build.gradle samples and rename runJar->bootRun 2013-12-10 11:10:04 +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

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.