[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-pmc] Add API method #canUpdateChildAttributes(...) for org.eclipse.jdt.core.ClasspathContainerInitializer
|
+1
Frederic
Fusier/France/IBM
@IBMFR To
Sent by: eclipse-pmc@xxxxxxxxxxx
eclipse-pmc-bounc cc
es@xxxxxxxxxxx
Subject
Re: [eclipse-pmc] Add API method
02/23/2007 01:29 #canUpdateChildAttributes(...) for
PM org.eclipse.jdt.core.ClasspathConta
inerInitializer
Please respond to
eclipse-pmc@eclip
se.org
GOALS/BENEFITS:
- Classpath containers want to defined if they are modifiable in a more
fine grained way than it is currently possible with
ClasspathContainerInitializer#canUpdateClasspathContainer.
As an example, in bug 166519 the JRE container needs to show access rules
in the UI. However these should not be modified by the user.
Native libraries however are not relevant and should not be shown.
The API to do this would go on ClasspathContainerInitializer and would have
a default implementation that is compatible with the current
#canUpdateClasspathContainer.
- The benefit would be that client could ask classpath container
initializer
which child attributes may be modified or not without knowing the container
itself and then allow/disallow the user to modify them appropriately.
AFFECTED BUGS:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=168077
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=166519
RISKS:
No known risks. Once this is added, the existing classpath containers will
respond correctly to this new API.
PERFORMANCE IMPACTS:
- will not have any impact
Cordialement/Regards,
Frédéric
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
