SNAPSHOT as next version about gradle-release HOT 10 CLOSED

Hi Tamas,
If you were using a -SNAPSHOT version the plugin should set the next version to be -SNAPSHOT automatically.

Eg. if you're current working copy has 1.0-SNAPSHOT, the plugin will release it as 1.0 (no snapshot), and set the next version to 1.1-SNAPSHOT automatically.

Is that what you're looking for?

from gradle-release.

Yes, that is what I need - but when I have version=1.0.0-SNAPSHOT in my gradle.properties, and execute 'gradlew release', it get 1.0.1 there.
I am using version 1.2 - is that the most up to date?

from gradle-release.

1.0.1 is in your gradle.properties at the end of a build or just your released artifacts have version 1.0.1?

from gradle-release.

It is in my gradle.properties. Also when running the release, when it prompts me for the next version, it also offers 1.0.1 by default...

from gradle-release.

You should be prompted twice. The first time will confirm "this" release version (which in your case will default to 1.0.1), and the second prompt will ask you for the next release number (which should be 1.0.2-SNAPSHOT in your case).

from gradle-release.

Ok, I think I know what happens...
I did get prompted twice, and the second prompt was 1.0.1 (no SNAPSHOT).
But since I am in the middle of setting up the build, I got some failures, and something probably was left in a transient state, confusing the plugin...
If I start clean (I mean really clean, like cloning the repo from scratch), then it works, I get -SNAPSHOT for the next release version.

from gradle-release.

Ah. Okay. That makes sense, but did the plugin not alert you to that fact? It should have printed something out about failures during the build task. Also, what version control system are you using? The plugin tries it's best to revert whatever changes it makes so I want to see if there's something preventing that from happening.

from gradle-release.

I am using Git, and I did get alerted that there was an error.
However, when releasing a snapshot version, and the 'uploadArchives' fails (I made it a dependency), even though the plugin says 'Release process failed, reverting back any changes made by Release Plugin', I can still see the pre-tag commit, so I guess that leaves the version without -SNAPSHOT, resulting in missing the -SNAPSHOT for the next version.
I do not see any errors in connection with the revert, the only errors I see are for the uploadArchives...

from gradle-release.

This is a know issue (feature?) of the current implementation which would be probably (at least there is a chance, but I'm not the author of this plugin) taken into consideration during the next big plugin rewrite.

from gradle-release.

@SFThomas @szpak is correct, this is a known issue. Thank you very much for explaining the situation though. I am planning on doing some major reworking to make this behave a lot more like the maven plugin which will probably mean keeping release status around in a file somewhere. It should keep track of where the process failed and the state of the release process. Then when you run it again, it'll just continue from where it left off. It should also mean that the push doesn't happen until the very last step.

from gradle-release.