Good day Subclipse Users,
I am developing a generic team integration enhancement to the Jupiter
(http://csdl.ics.hawaii.edu/Tools/Jupiter/) code review plug-in. The goal is
to track active change sets in order to auto-populate a code review request
for the files in a change set. I need to track the revision number for each
file in a change set and to do this have been using code like:
String version = null;
for (Iterator it = activeChangeSetManagers.iterator(); it.hasNext();) {
ActiveChangeSetManager activeChgSetMgr = (ActiveChangeSetManager) it
.next();
if (activeChgSetMgr instanceof SubscriberChangeSetManager) {
Subscriber subscriber = ((SubscriberChangeSetManager)
activeChgSetMgr)
.getSubscriber();
try {
SyncInfo syncInfo = subscriber.getSyncInfo(resource);
if (syncInfo != null) {
version = syncInfo.getLocalContentIdentifier();
break;
I find that the call to SyncInfo.getLocalContentIdentifier() always returns
the string "BASE" for a versioned file, not the revision number. The CVS
Team Provider always returns the CVS version number and it seems to me that
it would be preferable (from my perspective at least) for Subclipse to be
consistent, i.e., to return the SVN revision number. Source-level debugging
suggests that the required revision number is available in the called
context and could probably be returned with minimal effort.
Does anyone have any opinions or insights on this?
Thanks,
Adrian Price
Received on Wed Apr 4 18:42:33 2007