Ja-micro is available on bintray so that you can simply pull it in as a dependency. Please see https://bintray.com/sixt/ja-micro/ja-micro. Ja-micro uses semantic versioning. Therefore, you should be safe to include ja-micro as a dynamic dependency if you are using gradle. For example, add this to your build.gradle dependencies closure: compile 'com.sixt.service:ja-micro:3.2.+' This will pull in the latest patch version automatically.

Introduction video

ServiceProperties, the service registry & micro dashboard

The framework itself can be built on a Mac. Service integration tests do not work very well, because the Mac support from Docker is not good enough. It is not recommended to depend on a Mac if you intend to run service integration tests and have consistent results.

(For official maintainers only)

• Do a complete build, including SIT ./gradlew clean build test-service:sIT
• Bump gradle.properties as appropriate (following semantic versioning concept)
• Ensure all files are committed
• Tag the build like this: git tag -a -m "3.2.16" 3.2.16
• Push the commit and tags together: git push --follow-tags origin (this push has to have other changes besides just the tag, or the travis build won't trigger)
• Watch the travis-ci build page https://travis-ci.org/Sixt/ja-micro