This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
headless_eclipse [2014/05/01 10:18] yann [Class-loading and Object Sharing] |
headless_eclipse [2014/06/18 05:52] yann [Known Problems] |
||
---|---|---|---|
Line 44: | Line 44: | ||
- | ===== Known Problems ===== | + | ===== Caveats ===== |
Line 67: | Line 67: | ||
==== Access Rules ==== | ==== Access Rules ==== | ||
+ | When using the ''Import-Package'' statement and if the plug-in shares some common package with another plug-in, Eclipse gets confused and claims that other plug-in cannot use classes in this package, even if it is exported by all the plug-ins involved. Therefore, it is important to have different packages, which can of defeat the purpose of having plug-in in the first place. It is true, though, that ''Import-Package'' statement, by instructing Eclipse to by-pass its class-loading mechanism, disturb this mechanism. | ||