Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| headless_eclipse [2014/06/18 06:07] – [Questions to Answer when Programmatically Calling Eclipse] yann | headless_eclipse [2025/01/15 21:40] (current) – external edit 127.0.0.1 |
|---|
| 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. | 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. |
| |
| | |
| | ==== Plug-ins Referenced in ''config.ini'' but Missing ==== |
| | |
| | The ''config.ini'' file contains, among other things, the locations of the plug-ins (actually, their JAR files or folders) required by an Eclipse application. If one of more plug-ins are missing, i.e., there is a discrepancy between the ''config.ini'' file and the folder containing the plug-ins JARs and folders, then Eclipse will throw an error and the "configuration area" will contain a log file detailing the missing plug-ins. |
