[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-core-dev] e4 Resources Kickoff Meeting
|
Hi,
I'm not sure two different resources that point to the same physical
location should share the same list of markers.
For instance, if a file is shared in two different projects, but because
of the projects settings (predefined symbols, for example) the file in
project A builds fine while the same file in project B has build errors,
it would be a mistake to show the file in project A as having the same
errors as well.
Does that makes sense?
Serge Beauchamp.
Freescale Semiconductor
James Blackburn wrote:
Then I'd like to walk through the wiki page, the Work Areas page that Martin
O. has prepared and see if there anything people have objection to, or items
they'd like to add. The wiki site is here:
http://wiki.eclipse.org/E4/Resources please take a look before the meeting.
One of the things that isn't on the list is how the Workspace
currently copes with multiple IResources which map to the same
filesystem Location. These occur when you're building projects using
linked resources, or have created multiple projects with overlapping
locations.
Currently Eclipse treats multiple workspace resources (with same
location) separately. They open to separate editors, have separate
local histories, have separate markers, etc. See:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=247647 for the sorts of
things that go wrong.
It seems very difficult if not impossible for ISVs to integrate
properly if the platform really gives you multiple IResources for a
given location (with findFilesForLocation()). It certainly seems
non-trivial to decide on which File a marker should be created, or
which IFile should be opened when all you've got is the path provided
by an external tool.
Am I naive in believing that if they really are the same file on disk,
they really should map to a single IResource (or multiple IResources
with the same set of attributes)?
Cheers,
James
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-core-dev
