gradle.properties is updated before the main 'build' task is run about gradle-release HOT 4 CLOSED

Let's consider following scenario. Your build is doing some file replacement to put version into them and then package into jar or war or whatever. So apparently you need your build to have already updated version before starting build target.

So I think the issue is about incorrect rollback procedure of plugin and not the design of behavior itself.

from gradle-release.

I manually tested the git revert functionality the plugin is using and I think it may be incorrect. I failed a build using my above example and then manually ran..

git reset --hard gradle.properties

..and git replies..

fatal: Cannot do hard reset with paths.

So, if I got that right, I think removing gradle.properties as a parameter to that command would work. It'll reset everything though. If the goal is to only ever discard changes to the gradle.properties file, I think git checkout gradle.properties would work better.

from gradle-release.

I think the git reset --hard is a remnant of when we tried to revert the whole directory, but then changed to just wanting to revert only the properties file. I think using git checkout gradle.properties is the correct way of doing this. Thanks!

from gradle-release.

Uploaded a new snapshot that will revert the gradle.properties file properly now.

from gradle-release.