Community
Participate
Working Groups
Build F3 We have code to test if a java element is on the class path of a project. If the java element is a project itself (we ask project.isOnClassPath(project)) the answer is somehow random (see bug 20051). Is this a deeper problem ?
Indeed the implementation of this API is weak when dealing with project references. It is iterating the pkg fragment roots, instead of the classpath entries. It only makes a difference for elements which are not directly part of the project elements (amongst its children). How critical is this for you ?
We released a work around for F3. In the case of project.isOnClassPath(project) we assume true which works in the special case of the ActionUtil.isProcessable method.
I'm not sure I understand where the problem is. When proj!=src, the project is NOT on its classpath. When proj==src, the project IS on its classpath.
Since there is a workaround, will try to understand Dirk's problem post 2.0.
Jerome's explanations make the PR obsolete. Closing
Reopening to mark bug as WORKSFORME.
Works for me.