This is an automated email from the ASF dual-hosted git repository. ningjiang pushed a change to branch spring-boot-2 in repository https://gitbox.apache.org/repos/asf/incubator-servicecomb-saga.git.
omit 332f626 SCB-429 Upgraded the Spring Boot version to 1.5.10 add 078fb18 SCB-429 Upgraded the Spring Boot version to 1.5.10 add 3483937 Added CONTRIBUTING.md add d71d1bc SCB-433 Updated the docker running setting new 8a29c87 SCB-410 Alpha Service upgraded to Spring Boot 2.0 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (332f626) \ N -- N -- N refs/heads/spring-boot-2 (8a29c87) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CONTRIBUTING.md | 43 ++++++++++++++++++++++ acceptance-tests/acceptance-pack/pom.xml | 22 ++++++++++- .../org/apache/servicecomb/saga/PackStepdefs.java | 11 +++++- alpha/alpha-server/pom.xml | 19 ++++++++++ integration-tests/pack-tests/pom.xml | 21 ++++++++++- .../pack-tests/src/test}/resources/log4j2.xml | 0 pom.xml | 2 +- saga-persistence/saga-persistence-jpa/pom.xml | 8 ++++ 8 files changed, 120 insertions(+), 6 deletions(-) copy {alpha/alpha-server/src/main => integration-tests/pack-tests/src/test}/resources/log4j2.xml (100%) -- To stop receiving notification emails like this one, please contact ningji...@apache.org.