Changed charge persistence so that only those charges which the user may
change are also persisted. This protects users better from breaking their
products than the previous readonly flag did, and also makes data migrations
much easier when changes are made to those charges.  It also makes it possible
to adjust "readonly" charges based on product parameters.

In the process switched from lists to streaming for transporting the charges.
20 files changed
tree: 072f122428b662c11285e5f736ae114dabaab272
  1. api/
  2. component-test/
  3. gradle/
  4. service/
  5. .gitignore
  6. build.gradle
  7. gradlew
  8. gradlew.bat
  9. HEADER
  10. LICENSE
  11. README.md
  12. settings.gradle
  13. shared.gradle
README.md

Mifos I/O Portfolio

Join the chat at https://gitter.im/mifos-initiative/mifos.io

This project provides product and case management for Mifos I/O. Products are described and “instantiated” for customers as cases.

Abstract

Mifos I/O 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.

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 - 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.