Checking in unresolved changes

Engineering Workflow Management source control uses an optimistic locking model that does not require a check-out operation before you can modify files or folders. All files in a sandbox are normally writable. Modified files remain private to your repository workspace until you deliver them.

About this task

Engineering Workflow Management source control tracks the changes that you make in your sandbox and displays them in the Pending Changes view. Each modified component in a workspace can include an Unresolved folder, an Outgoing folder, or both. These folders contain the changes you have made.

Changes that you make to files and folders in your Eclipse workspace accumulate in the Unresolved folder for the component until you check them in to a change set. (If you have selected the Auto check-in local changes preference, then the changes are automatically checked in to the current change set for the component and are displayed in an Outgoing folder. For more information, see Choosing automatic or manual check-ins.) Changes listed in an Unresolved folder remain private to your Eclipse workspace until you check them in.
Note: If you use external tools (ones that are not part of the Eclipse IDE) to modify files and folders, you typically need to refresh your workspace before Eclipse (and Engineering Workflow Management source control) can detect that modifications have been made. If resources you have modified are not visible in an Unresolved or Outgoing folder, navigate to the project in the Eclipse Navigator view (or any Eclipse view that lists the projects in your workspace), right-click it, and click Refresh. You can also refresh the project or any of its subfolders by clicking it and pressing the F5 key. On Windows, you can also set a preference to automatically detect changes made outside of Eclipse. For details, see the procedure below.


  • Expand the Unresolved folder to see its contents.
    • To check in the entire set of unresolved changes to the current change set, right-click the Unresolved folder and click Check-in all.
    • To check in an individual item in the Unresolved folder, right-click it, click Check-in, and click an existing change set to receive the change, or click New change set to create a change set. (A file or folder in a component cannot be part of more than one active change set. When a file or folder is included in an active change set, all changes to it become part of that change set whether or not the change set is current, and changes to that file or folder cannot be explicitly checked in to a new change set until the active change set that includes it is completed.)
  • Optional: On Windows, to automatically detect changes made outside of Eclipse:
    1. Click Window > Preferences.
    2. On the Preferences page, navigate to Team > Jazz Source Control > Local Changes.
    3. On the Local Changes page, select Automatically detect changes.
    4. Click Apply.
      Note: To preserve history, use Eclipse to rename or move files and folders.