I think you can select the root of the project and commit all changes in your workspace in one commit. Secondly you should always test your software after any changes and before commiting. Even if the only thing you do is use one of the builtin refactoring: there could be a bug in a refactoring or the refactored code not completely equivalent to your old code. That is why all VCS I know do not commit immediately on change. Even if you are developing by yourself, it is a good practice to check in only complete changes that works.
My 2 c Jacques "Adam Goldband" <[EMAIL PROTECTED]> wrote in message aiuuu3$ii5$[EMAIL PROTECTED]">news:aiuuu3$ii5$[EMAIL PROTECTED]... > I would love it, if say I was making a method name change that effected a > whole batch of files (java, jsp, or whatever) if I could be prompted to > commit all those files when I am done doing the refactoring. > I often find it cumbersome to keep track of every place I made the change... > so in most cases I would just like to be able to commit that change right > then and there. > > Thanks... > > adam > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
