Google Git
Sign in
apache / fineract-cn-default-setup / 59669201f0d025c2eaa03dc30badeb12bb039a13
commit59669201f0d025c2eaa03dc30badeb12bb039a13[log] [tgz]
authorIsaac Kamga <ikamga@apache.org>Mon Sep 02 23:25:00 2019 +0100
committerGitHub <noreply@github.com>Mon Sep 02 23:25:00 2019 +0100
treef8c867be4c867c957bbb34f5198649ebc866a399
parentdb525d09c4e93305948b049a54015a90504932b0 [diff]
parente7f5fe56d907ce0f8a407c9ce0d74e551174345e [diff]
Merge pull request #8 from Izakey/FINCN-155

Prepare default setup for PostgreSQL migration
tree: f8c867be4c867c957bbb34f5198649ebc866a399
  1. accounting/
  2. gradle/
  3. .gitignore
  4. .travis.yml
  5. build.gradle
  6. gradlew
  7. gradlew.bat
  8. HEADER
  9. LICENSE
  10. NOTICE.txt
  11. README.md
  12. settings.gradle
  13. shared.gradle
  14. travis.sh
README.md

Apache Fineract CN default setup Build Status

This project provides resources which can be used to create a default setup for microservices in Apache Fineract CN deployment. It is dependent on the apis and importers of those microservices.

Abstract

Apache Fineract CN is an application framework for digital financial services, a system to support nationwide and cross-national financial transactions and help to level and speed the creation of an inclusive, interconnected digital economy for every nation in the world.

Steps needed to create a default setup for a new microservice

  1. Create a module with the same name as the microservice. Add it to settings.gradle, and build.gradle of the composite build.

  2. Place the csv files in subfolder of main/resources

  3. Change build.gradle of your module to reference the importer of your microservice in compileTest

  4. Write a test which checks the format of your csv files to prevent data corruption. See accounting/ImportTest for an example of how to do this.

Versioning

The version numbers follow the Semantic Versioning scheme.

In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.

  • BUILD-SNAPSHOT - A release currently in development.
  • M - A milestone release include specific sets of functions and are released as soon as the functionality is complete.
  • RC - A release candidate is a version with potential to be a final product, considered code complete.
  • RELEASE - General availability indicates that this release is the best available version and is recommended for all usage.

The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:

1.2.3-BUILD-SNAPSHOT
1.3.5-M.1
1.5.7-RC.2
2.0.0-RELEASE

License

See LICENSE file.