Google Git
Sign in
apache / fineract-cn-template / c6b23d9f89d5e3412ac7e94721fdc01e5ee2eeb6
commitc6b23d9f89d5e3412ac7e94721fdc01e5ee2eeb6[log] [tgz]
authorMyrle Krantz <myrle@apache.org>Fri Apr 13 16:53:27 2018 +0200
committerMyrle Krantz <myrle@apache.org>Fri Apr 13 16:53:27 2018 +0200
tree28848ff546735479780d93e0605c2142fc4ca692
parent54482d06928b7a28c4f937e3f2ced35dc41d48db [diff]
Adjusting to package name changes in upstream repositories.
12 files changed
tree: 28848ff546735479780d93e0605c2142fc4ca692
  1. api/
  2. component-test/
  3. gradle/
  4. service/
  5. .gitignore
  6. build.gradle
  7. gradlew
  8. gradlew.bat
  9. HEADER
  10. LICENSE
  11. NOTICE.txt
  12. README.md
  13. settings.gradle
  14. shared.gradle
README.md

Apache Fineract CN Template

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

This project provides a template layout for all Apache Fineract CN 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 turn the template project into a real project

  1. Git clone template into {project name} folder

    git clone https://github.com/apache/fineract-cn-template.git {project name}

  2. Delete .git

    rm -rf .git

  3. Open settings.gradle and replace value of rootProject.name with {project name}

  4. Open root build.gradle and replace value of version with 0.1.0-snapshot

  5. Create Gradle wrapper

    gradle wrapper

  6. Open all module specific build.gradle files (api, service, and component-test) and replace value of group with io.mifos.{project name}

  7. Import project into IDE

  8. Rename all io.mifos.template packages to io.mifos.{project name}

  9. Open SampleRestConfiguration and SampleServiceConfiguration, adjust @ComponentScan to reflect the new package name

  10. Open application.yml and replace server.contextPath with /{project name}/v1/*

  11. Open bootstrap.yml and replace spring.application.name with {project name}/v1/

  12. Open SampleTest and replace constructor argument of TestEnvironment in line 80 with {project name}/v1/

  13. Run SampleTest

  14. Replace the contents of the README with text describing your new project.

  15. Happy coding! ; o)

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.