History

Sebastien Deleuze ab6c8dfee3 Use org.springframework.boot groupId in spring-boot-samples

Use org.springframework.boot instead of ${project.groupId}
groupId in order to make it easier to use spring-boot-samples
modules as a starting point for new projects.

2014-03-07 17:02:20 +00:00

src

Fix test that fails because of pretty printing

2014-01-31 16:38:09 +00:00

build.gradle

Update Spring repository url in Gradle samples

2014-03-04 13:15:41 +00:00

build.xml

Update ant example to 1.0.0.BUILD-SNAPSHOT

2014-01-21 10:22:42 -08:00

ivy.xml

Update ant example to 1.0.0.BUILD-SNAPSHOT

2014-01-21 10:22:42 -08:00

ivysettings.xml

Add basic build.xml to actuator sample

2013-12-23 14:50:58 +00:00

pom.xml

Use org.springframework.boot groupId in spring-boot-samples

2014-03-07 17:02:20 +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.