This file contains information which is relevant for the development of the APIM CLI. For example, how the APIM CLI is released or integration tests work.
The version management concept is based on the develop and master branches. New features, bug fixes, etc. are created in appropriate branches and merged into the development branch when they are ready for the next version. This means that the develop branch is actually stable or buildable at all times.
- A Windows, Linux or Mac workstation with Git installed.
- Write access on master and develop on https://github.com/Axway-API-Management-Plus/apim-cli
- A Sonatype user with access to https://s01.oss.sonatype.org
- And access to project:
com.github.axway-api-management-plus
- Create a JIRA-Ticket to get access (https://central.sonatype.org/publish/publish-guide)
- And access to project:
- GnuPG for Code-Signing (e.g. https://gnupg.org/)
- Apache Maven 3.6.3 or higher
For the release, develop is merged into Master and the release is generated on Master with Maven.
git clone https://github.com/Axway-API-Management-Plus/apim-cli.git
git checkout master
git merge develop
vi CHANGELOG.md # set the release date and version number
git commit
git push
- Run Github action Release API CLI on github and Maven repository
git checkout develop
git merge master
git push