|Possible bug in Target Platform handling [message #959462]
||Fri, 26 October 2012 18:42
| Eric Rizzo
Registered: July 2009
Eclipse 3.8 (although I've also seen this in earlier versions)|
It seems that the target platform infrastructure has problems handling a TP that contains the same bundle in multiple locations. For example, my TP includes different directory locations for Eclipse 3.8 SDK, Orbit bundles, WTP 3.4.1, and the 3.8 Delta Pack. Setting this TP on my workspace causes problems resolving bundles that are present in more than one of those locations. For example, both the Delta Pack and SDK locations include the platform-specific SWT bundles and fragments. When the Delta Pack is included in the TP, even if I un-select the SWT bundles that are already in the SDK location, none of my projects can resolve any SWT classes (nor can I open SWT classes with Ctrl+Shift+T, nor do they show up in the Plugins view). This happens regardless of what bundles I actually have selected from the Delta Pack location, even if everything is un-selected.
If I totally remove the Delta Pack directory from my TP, then SWT can be resolved by my workspace code again.
This is only one example, I have the same problem with other bundles that are duplicated in more than one directory location in my TP - for example, org.apache.log4j is in both SDK 3.8 and WTP 3.4.1 - as soon as WTP is included in my TP, no workspace code can resolve log4j classes any more.
Is this a known problem/limitation? I've seen this going back several versions of PDE (at least back to Galileo) and with 3 different code bases and countless workspaces.
Any ideas on how to troubleshoot it and/or work around it?
[Updated on: Fri, 26 October 2012 18:44]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01626 seconds