CODEWITHSUNDEEP
gradlereleasesemantic-versioninggradle-release-pluginaxion-release-plugin
Michal Kordas
Michal Kordas

Reputation: 10925

Gradle Release Plugin for projects not following semantic versioning scheme

I'm writing a components that will be working with some particular version of platform. Let's say the platform is in version 1.18.0, then I want to release component e.g. with version 1.18.0.1, then 1.18.0.2. If platform updates I want to release 1.19.0.1 etc. This of course breaks semantic versioning.

I need a release plugin for Gradle, that supports this versioning scheme, but it uses only tags to store version (no commits during release, so I cannot use https://github.com/researchgate/gradle-release).

There are two plugins that from what I've seen enforce semantic versioning so I cannot use them:

How can I achieve basically the same as axion-release-plugin but with my custom versioning scheme that does not follow semver?

Upvotes: 2

Views: 1739

Answers (1)

Hillkorn
Hillkorn

Reputation: 786

Actually https://github.com/researchgate/gradle-release could do what you want. Disable the tasks you don't need in your build.gradle

preTagCommit.enabled = false
commitNewVersion.enabled = false

At the end you should have only the tag in git. But why not having it committed to git? You will need the new version at least I think (would be commitNewVersion).

Upvotes: 1

Related Questions