Allow Editing Without Checkout Considerations

We recommend the use of the Allow editing without checkout preference because it improves performance and best suits refactoring operations.

The following considerations apply if you do not use the Allow editing without checkout preference:

If you perform any refactoring operations on *.java files, a check-out occurs followed by the corresponding refactoring operation.
If you perform any refactoring operations on files that result in content change of the files, a check-out occurs followed by the corresponding refactoring operation. For example, renaming a java file from a java perspective results in the change of the class name (check-out occur followed by rename operation).
You cannot perform refactoring of a Java package because refactoring of a Java package will result in a check-out of all the files under that package.
If a refactoring operation fails after the check-out for update of files, the files remain reserved and you need to release the files explicitly.
If a refactoring operation fails, a Refactor Error dialog can appear that has Undo and Abort options. This dialog does not impact the workspace; you can click Undo or Abort to close the dialog.