Automatically suggest version updates for modified projects

[vladdu]

For projects in a SCM, one could have an option in the UI that selects all projects that have changed since the latest release and increment their versions according to the current policy.

Feature projects would get updated according to the changes in their plugins.

If there is a manual change to the version that is larger than the change that would be suggested, then tha manual one takes precedence.

[b8]

In our company, we had such a script that did that but for the old eclipse PDE build (using a simple svn diff).

Currently, we mostly build all the bundles because it's tricky to find out whether the classes needs to be recompiled even when their source code did not change. We had some evil cases due to refactoring in dependency bundles.

So, after a release we increment all bundles to the next micro (bugfix) number snapshot.

I'd prefer version tiger itself wouldn't do too much tricks with other tools like svn/git to keep it simple.

[vladdu]

Theoretically, it's possible to follow the dependency chain and update version only for the plugins that could be affected by a change, but I think it would be too much work for too small gain.

Feel free to close this if you think it falls outside the scope of the project.