| Should path variables be handled per workspace or per resource? [message #634517] |
Fri, 22 October 2010 00:26  |
Eclipse User |
|
|
|
Hi,
In my current task, that I have to export and import project information
containing the path variables active in the workspace.
And I have found something confusing:
- when using the workspace as a user it seems as if the path variable
were global setting stored on workspace level.
- But when I try to reach them from code it seems as if they were
resource specific.
For example if I reach them like this I always get an empty array of
String -s:
ResourcesPlugin.getWorkspace().getPathVariableManager().getP athVariableNames();
However if I have an IFile object and use it like this, I always get the
list visible to me in the menus:
file.getPathVariableManager().getPathVariableNames();
But in this case I always receive the exact same list for every resource !
Which is the better understanding, I should use in my implementation?
Can I assume, that there is only one list of path variables per workspace?
Or should I assume, that sooner or later this will change into ... like
a hierarchical structure, based on the folders?
Thanks for any help,
Kristof
|
|
|
|
Powered by
FUDForum. Page generated in 0.04551 seconds
Home