Why hardcode "Always auto increase build number"? Make it optional!

[romanr]

Thank you for the great plugin, it's most comprehensive and developer friendly!

I am not sure how is it supposed to work, but during development the project is run in debug mode tens/hundreds of times. And on every such run GrabVer is activated and ran.
Resulting in version.properties unnecessarily updated on every single run.
Resulting in developer have to reset/revers version.properties before every commit. It's highly annoying.
AmI doing something wrong, I don't think it's intended to become annoyance for developer to revert or ignore version.properties during every commit operation.
Shouldn't there be an option to not increment build number?

[davideas]

Ok understood. Originally the plugin was intended to be used as single user, but it became quite famous, and I am also having this merge to do when I work in team.
Basically the user who is responsible of deployments should be the one that takes care of the versioning, others can ignore it.
As you say, the activation is at each build, in fact, one of the main purpose of this plugin is to keep track of build number somewhere, this is central and I would prefer to not remove it.

Now for team work we might find an alternative solution, I need to think how I can do it.

Thanks for your friendly message and keep following.