snowdrop/spring-boot-bom

Name: spring-boot-bom

Owner: Snowdrop

Description: null

Created: 2017-02-28 14:24:46.0

Updated: 2017-07-12 15:26:56.0

Pushed: 2017-12-12 12:01:54.0

Homepage: null

Size: 81

Language: null

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Introduction

This project contains different Spring Boot BOMs created to simplify the developement of Microservice Spring application top of the Openshift/Kubenetes Cloud platform. They are used by our opinionated examples called boosters which contains Spring Java code implementing a pattern, use case or capability. Such booster will help you to develop Cloud Native application running on Openshift/Kubernetes.

A branch exists for each version of Spring Boot currently supported; 1.4.x, 1.5.x, 2.x …

To modify a pom, checkout the appropriate branch git checkout sb-1.4.x

Releasing

Issue first a dry run to control the changes

release:prepare -DdryRun

Convention to follow :

 is the release version for "spring-boot-1.4-bom"? \
rg.jboss.snowdrop:spring-boot-1.4-bom) 1: : <DIGIT>
 is SCM release tag or label for "spring-boot-1.4-bom"? \
rg.jboss.snowdrop:spring-boot-1.4-bom) spring-boot-1.4-bom-1: : sb-1.4-<DIGIT>
 is the new development version for "spring-boot-1.4-bom"? \
rg.jboss.snowdrop:spring-boot-1.4-bom) 2-SNAPSHOT: : <NEXT-DIGIT>

e <DIGIT> corresponds to the number without `-SNAPSHOT` and `<NEXT-DIGIT>` is the next digit available

Before to release, check within your ~/.m2/settings.xml file that you have a <service><id> for jboss-releases-repository defined which contains your credentials

ver>
d>jboss-releases-repository</id>
sername>userName</username>
assword>passWord</password>

Then release using maven release plugin

release:perform