In order to move away from an aligned versioning across all Bahmni components (0.91-SNAPSHOT, 0.92-SNAPSHOT…), and to allow other projects depend on individual Bahmni components, we should move to:
- independent version number for each module/component. Each module is then referred by its required version in a distribution
- proper Maven-like releases, where “-SNAPSHOT” is removed on the release point, a commit is made on this new version (+ a tag), and the next development added with “-SNAPSHOT” version is then set.
- use SemVer
This is documented and implemented for Bahmni IE Apps BAH-1028.
However, Bahmni IE Apps 1.0.0 does not get deployed by the Bahmni CI.
<distributionManagement> <snapshotRepository> <id>repo.mybahmni.org</id> <name>bahmni-artifactory-snapshots</name> <url>s3://repo.mybahmni.org/artifactory/snapshot</url> </snapshotRepository> </distributionManagement>
I am guessing we should add a repository section for the released artifacts.
Note, I also thought we don’t use the
s3:// protocol anymore and use
https:// instead. Is this correct?