nebula-release-plugin icon indicating copy to clipboard operation
nebula-release-plugin copied to clipboard

Custom version in contrary to nebula-release-plugin inferred version

Open VITOLDO opened this issue 6 years ago • 0 comments

Is there any way to dynamically set some other version despite having some other in git flow?

Example: I have a GIT flow which had tags in master: v1.1.0.3 v1.1.0.2 v1.1.0.1 v1.1.0.0 v1.0.4 v1.0.4.3 v1.0.4.2 v1.0.4.1 v1.0.4.0 And at some point I needed a hot fix for v1.0.4

So what do i do: I'm creating branch from v1.0.4 and bumping patch version. So it' now v1.0.5.0. When I'm trying to build project - nebula-release-plugin detects version 1.1.0 as a basic version.

Note. I've changed the way how version is taken in finalSetup hook.

So one question is why it detects 1.1.0 instead of 1.0.5? (I think it's due to how git tag -l works) But most important: How to dynamicly change version in gradle config? (For example in some task, but in the way that finalSetup will also see those changes)

VITOLDO avatar Mar 06 '18 16:03 VITOLDO