Community
Participate
Working Groups
It looks like we are relying on an internal JDT class to process filters. This pulls in JavaProject and ClasspathEntry, both internal. I am unclear as to what exactly this filter processing does, but if we really need it we should encapsulate it in a non-internal wtp class so that we make internal jdt references from one place instead of many places. See org.eclipse.jst.common.jdt.internal.classpath.FlexibleProjectContainer for the usage of jdt.internal.core.util.Util class.
Just changing subject "key word" to fit conventions. Chuck, can this be fixed in 151?
BTW, you mention "non-internal wtp class" ... but, non of our API should depend on another projects internals, if that what you meant. I agree, would be nice to have centralized, so its clearer what and where the dependancy is. I'm just recommending we not imply it is API.
Ideally we eliminate the reliance on internal api. If it cannot be eliminated, we should at least consolidate its usage in a WTP utility class.
Let's count all internal usage as "major" since it prevents the function of "easy safe binary compatible updates". (or, at least, reduces the probablity).
The mentioned class currently seems to reference only public API from JDT