Within a project, if a linked resource (a folder) is created that points
to a folder in a different working copy, the Subclipse integration does
not recognize any resources within the linked resource as controlled by
SVN. To reproduce:
2 Working copies on the filesystem:
(working copy "project)
/workingcopies/project/
/workingcopies/project/.project
(working copy "TestFiles")
/workingcopies/TestFiles/Source/
/workingcopies/TestFiles/Source/file1.c
/workingcopies/TestFiles/Source/file2.c
/workingcopies/TestFiles/Includes/
/workingcopies/TestFiles/Includes/file1.h
Within Eclipse:
project/
src (linked to --> /workingcopies/TestFiles/Source)
inc (linked to --> /workingcopies/TestFiles/Includes)
The point is, even though the project is controlled in Subversion, and the
linked resources are controlled, Subclipse doesn't allow any SVN
operations on resources in the linked folders.
After investigating this problem, I received word from the Subclipse
development team that this behavior is actually recommended by the Eclipse
API. I found this surprising as the ClearCase SCM Adapter I had been
using for IBM ClearCase integration does support linked resources. I
suppose I just expected all team integrations to work the same.
This feature will unlikely be added to the Subclipse plug-in in the
future. In light of that, has anyone solved a problem like this in
Eclipse? Does Subclipse have good support for externals? Do recursive
commits in Subclipse commit the externals? Basically, I am looking for
the downside.
Thanks to Mark for answering my initial questions.
Chad Barnes
Rockwell Collins, Inc.
Received on Wed Mar 15 20:45:05 2006