K8SSAND-151 ⁃ Fix pom versioning to match release versioning

k8ssandra / management-api-for-apache-cassandra

RESTful / Secure Management Sidecar for Apache Cassandra

Apache License 2.0

71 stars 51 forks source link

K8SSAND-151 ⁃ Fix pom versioning to match release versioning #94

Open emerkle826 opened 3 years ago

emerkle826 commented 3 years ago

Right now, the POM version is still sitting at 0.1.0-SNAPSHOT, though the release tagging is now at v0.1.23. The POM should be updated to reflect the next release tag.

BONUS: setup a process to change the POM version from a SNAPSHOT version into a proper release version when tagging (this is likely a bit more involved).

┆Issue is synchronized with this Jira Story by Unito

burmanm commented 2 years ago

Once done, the maven version can be queried and returned in the getFeatureSet endpoint (#142) to get the management-api version

emerkle826 commented 2 years ago

Also, to make sure it doesn't get lost, when the versioning is fixed, we'll have to revisit Medusa test steps here: https://github.com/thelastpickle/cassandra-medusa/blob/master/tests/integration/features/steps/integration_steps.py#L1283-L1301 Currently, the Medusa tests extract the Agent jarfile into CCM, and the code expects the jarfile to be named with 0.1.0-SNAPSHOT.