| Product export wizard problem [message #448346] |
Fri, 21 April 2006 08:49  |
Eclipse User |
|
|
|
first I like to say sorry for posting the nth question regarding the product export wizard, but I am really desperate!
I've read nearly any post regarding compile problems ("The import x.y.z cannot be resolved") when exporting the product and I've checked Manifest.mf and build.properties many times. I even created three dummy plugins that do nothing but depend on each other the same way that my product does. The situation:
I have an RCP application plugin A and two plugins B and C. B contains sources and 3rd party libraries, which it exposes to A and C. A and C depend on B. C also depends on A (some base classes are defined in A).
I am able to export all plugins one by one, but if I try to export the whole product (based on plugins) I'll get compilation problems.
All classes of A that depend on classes of B cannot be compiled because the imports cannot be resolved. It's the same with plugin C. There all imports from A and B cannot be resolved. In short: No import from another plugin can be resolved.
All stated packages are exported by the their plugins manifest and are imported in the dependend plugins manifest. The dummy plugins do not show this behaviour, therefore I have no clue what's going wrong.
Is it possible to debug the exports compile process to see the classpath settings at compile time?
Can it be a problem of compile order?
To avoid the export wizard, I need an Ant file that will do the same. Where can I find such a file?
Thanks for 'listening' to me. I would be very glad, if you have useful hints or solutions for me.
Torsten
|
|
|
|
|
| Re: Product export wizard problem [message #448373 is a reply to message #448372] |
Mon, 24 April 2006 07:17  |
| Eclipse User |
|
|
|
Hello Daniel,
> since you have a very basic problem, I would start
> with some questions:
> ...
> Are all of these constraints fulfilled?
Yes, they definitely are fullfilled. I have defined the dependencies only via the manifest and used update classpath to set the project classpath.
The exported packages lists of my plugins contain all packages that should be visible to other plugins.
Furthermore the 3rd party libraries (spring framework) are exported via runtime page and I have added the '.' to the runtime tab classpath.
The jars produced by the export wizard are containing everything that's necessary. Nonetheless I got compile errors until I followed Alan Greens hint. Now everything works fine.
Torsten
|
|
|
Powered by
FUDForum. Page generated in 0.03586 seconds
Home