What do the arrow icons in Subclipse mean?
What do the icons in the following screen capture mean? The icons are from Subclipse, an SVN plugin for Eclipse.
I'm not asking about the base file icons, I know those (HTML file and Java source file). I'm asking about the right-pointing dark gray arrows, which are labeled "outgoing." What does that imply? Outgoing from the IDE to the repo, or outgoing from the repo to the IDE? Why are there minus signs inside the arrows? Sometimes, I see plus signs instead; other times, just empty arrows. What's the difference?
There are also left-pointing blue arrows and double-headed red arrows; what do those mean? What about cases when they contain other symbols, like - and +?
Note: This question has been edited pretty drastically. Normally I wouldn't change so much, but it had nearly no activity and was a dupe. The original question asked for an "icon glossary" that would explain all or most of Subclipse's icons, similar to this one for Eclipse. I'd still love to know about one of those, but there just doesn't seem to be one out there.
Answer
When working with the Subversion repository, remote changes (those on the repository) are incoming changes (remote → local), while local changes are outgoing changes (local → remote).
In views that compare the local and remote copies, incoming changes are denoted with a blue, left-facing arrow, while outgoing changes are denoted with a gray, right-facing arrow. These arrows may be decorated to indicate more specific operations.
The Package Explorer view, on the other hand, indicates a file's status with a different set of icons representing its local state. These icons are the ones most commonly seen, so let's start with them:
- A file ignored by version control. You can control what resources will be ignored by going to Window → Preferences → Team → Ignored Resources.
- A file not under version control. These are typically new files that you have not committed to the repository yet.
- A versioned file that needs to be added to the remote repository. These are typically files you have either renamed, or moved to a different directory.
- A deleted folder. These are folders that you have deleted locally without yet committing the changes to the repository. Note that files are usually removed from the view when they're deleted locally, so they are normally not seen with this icon.
- A file with no local changes.
- A file with local, uncommitted changes.
- A locked file.
- A file that needs a lock to be edited. These are typically files that cannot easily be merged (i.e. binary files), but may have many editors. A file needs a lock when its svn:needs-lock property is set, and Subversion will attempt to make these files read-only in the file system to enforce proper lock negotation.
- A conflicted file. These are typically files that had a commit/update conflict that you marked to resolve later.
- A file that has a tree conflict. These are typically files that have local changes, but have since been moved, removed, or renamed in the repository since the last local copy update.
- A file that is external to the project. Linked external files cannot be committed to the repository.
- A file that has been switched. These are files which belongs to a different working copy than their local parent directory.
In a synchronization view (e.g. via Synchronize with Repository or Commit), as previously described, there are icons which indicate which direction a change is occurring in as well as additional information about that change. These are described below:
Outgoing
- A file whose contents have been modified and will be committed to the repository.
- A file that will be newly added to the repository. This may coincide with a file removal in cases where a file is moved or renamed..
- A file that will be removed from the repository. This may coincide with a file addition in cases where a file is moved or renamed.
- A file with property changes, in the Commit dialog. On the Synchronize tab, property changes are currently reflected as a normal file modification ().
Incoming
- A file that has content changes committed to the repository that will be applied to the local copy.
- A new file that will be added to the local copy from the repository. Like the outgoing file addition, this may be the result of a move or rename.
- A file that will be removed from the local copy because it has been removed from the repository. Like the outgoing file removal, this may be the result of a move or rename.
Conflict
- A file that has been changed in both the local copy and repository independently, causing a need for conflict resolution. Fixing this condition involves opening up the conflict view or forcibly overwriting changes locally or remotely.
- A file that has a tree conflict. This can occur when there are new changes to a file on one end (either local or remote), and the file is moved, removed, or renamed on the other.
Finally, the Synchronize with Repository option opens the Synchronize tab (
) with the following buttons:
- Synchronizes the local copy with the currently selected repository when clicked. Selecting from the drop-down allows switching between different remote code bases.
- Shows only incoming changes (remote → local).
- Shows only outgoing changes (local → remote).
- Shows both incoming and outgoing changes (remote ↔ local).
- Shows conflicting changes.
- Updates all local resources with incoming changes after prompt.
- Brings up the commit dialog to commit all outgoing changes.
- Breaks up the change lists by revisions.
There are a few other views which weren't covered that have additional icons, but this should hopefully be a good start. Let me know if there is anything important missing, or any of these descriptions seem to differ from your actual experience.