Community
Participate
Working Groups
Created attachment 139839 [details] screen shot of package explorer Build ID: 3.5 RC4 Steps To Reproduce: Please check the bug 280888 : after migration to the 3.5 from 3.4, we can't run incremental builds anymore, because PDE adds the external /lib folder to the plugin required libraries. More information: See attached screen shot and also project settings attachment to the bug 280888: https://bugs.eclipse.org/bugs/attachment.cgi?id=139766 With 3.4 on same code base the issue does not occur.
P.S: 1) the local "bin" entry (with generated classes) is also unexpected 2) in the workspace, NO ONE plugin references to the external folders, except the manifest entry in com.verigy.itee.svc.unoaccess plugin (see attachment 139766 [details]): external:$XOC_SYSTEM$/lib/SessionServiceManager.jar $XOC_SYSTEM$ is specified in the system environment: > echo $XOC_SYSTEM > /vobs/zenith/workspace/system This SessionServiceManager.jar is usually missing, so that the second one (local) is used for compilation (the external one is used for debug purpose only). This setup works just fine with 3.4 / 3.3. I guess PDE gets confused by this external:$XOC_SYSTEM$ entry, cannot resolve it and just uses "/lib" directory. Why "bin" is added too, is still a mistery for me.
The "Referenced Libraries" container is not a dynamic classpath container. This is just a group of entries from the .classpath file of kind="lib". PDE generates the "lib" entries when jars are added to the "Runtime > Classpath" entries in the manifest editor, but these entries are standard classpath entries understood by jdt.core. There entries are static - I don't see "lib" or "bin" in your .classpath file,so I'm not sure how/why they are appearing.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
*** This bug has been marked as a duplicate of bug 563819 ***
