Hi Subclipse developers,
I would like to know why linked eclipse resource seem to be ignored by your
"Linked resources" are a wonderful way to reorganize its own eclipse project
file hierarchy by creating its own folders "linked" to a physical path.
The only drawback is that any given "linked resource" (file or directory) can be
displayed several times within an eclipse project.
Why do you ignored linked resources ? As far "configuration management" is
concerned, either the physical path of a linked resource is within a repository
path hierarchy, or it is not. If it is, all subversion options should apply to
I successfully manage to make linked resource recognized by subclipse plugin
(0.9.31 on an eclipse3.1RC3) by:
- making a LocalResource not ignoring a linked resource (function isIgnored of
- adding a functon getResource(IPath pathEclipse, boolean isDirectory,
IWorkspaceRoot workspaceRoot) to
(it try to getContainerForLocation or getContainerForLocation first, then if it
is null, tries to findContainersForLocation or findFilesForLocation and returns
the first resource found)
- replacing all other calls to getContainerForLocation or
getContainerForLocation by File2Resource.getResource
I believe the code could be enhanced to take into account the multiple resources
send back by the findXXXForLocation functions, but my quick fix proposition
always returns one resource: the first that is found.
So again, my question: why this eclipse plugin denies eclipse users to take
advantage of linked resources feature ?
-- Daniel Chaffiol
dchaffiol [at] free [dot] fr
Received on Fri Jun 24 07:03:44 2005