Hi all,
I'm working on providing something related to the story of "multiple
classpath per projects" in JDT. My idea and POC relies on consider
a m2e scope as a JDT classpath container -so there would be a "Maven
compile dependencies" and another "Maven test dependencies"
container, and to set up attributes to restrict "visibility" of
those containers to the right source folder and of a builder that
check referenced type are visible for a given source folder. This
story is related in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486035 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486032#c7 and I have
an early stage implementation working.
I did chat a bit with Fred on this topic and he told me that an
issue of multiple classpath container can be the order of the jars.
I was a bit surprised as it's the first time I hear about it. Do you
have any example to provide on this topic that wouldn't work with a
multiple classpath containers approach? And do you know how likely
this is to happen, and how severe could be an issue on this topic;
basically how much importance we want to give to such issue compared
to the usability improvement of multiple container?
Thanks in advance,
|