Summary: | Compiler errors after analyzing code and adding dependencies | ||
---|---|---|---|
Product: | [Eclipse Project] PDE | Reporter: | Wassim Melhem <wassim.melhem> |
Component: | UI | Assignee: | Brian Bauman <baumanbr> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | jeffmcaffer, tjwatson |
Version: | 3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Wassim Melhem
2006-03-27 02:55:16 EST
Note that the errors appear after you remove the bundles from the secondary dependency list and save. This actually will work at runtime if you leave the secondary dependencies so that you can compile successfully. I think this is related to JDT being too strict for our comfort. See bug 122915 for more information. I would not recommend PDE start adding more imports that what is needed at runtime here. That will only cause different defects to be opened for you. Thanks Tom. this is then a dup of bug 73957 where the compiler needs more stuff on the classpath than the runtime. *** This bug has been marked as a duplicate of 73957 *** but does this mean that the UI should be reexporting runtime? In the past we have said that if you expose someone else's API on your API then you should rexport to ensure that your consumers get the same one as you got. Presumably this would solve the problem here and be somewhat more accurate Reexporting a dependency plays no role in this strictly Import-Package-oriented scenario, does it? d'oh I missed that part. Never mind... |