| plugins with additional jar libraries [message #243679] |
Sat, 22 May 2004 16:38  |
Eclipse User |
|
|
|
Hi,
I have a plugin that has in addition to the normal source folder a
ready-compiled jar file which is defined in the plugin.xml file as a
runtime library (as well as the bundle classpath in the manifest.mf),
too. This worked fine with m8 but I have problems with this setting with
m9. Is this setting no longer supported or does it look like a bug?
Thanks for the help,
Martin
|
|
|
|
|
| Re: plugins with additional jar libraries [message #243961 is a reply to message #243956] |
Sun, 23 May 2004 10:16  |
| Eclipse User |
|
|
|
Hi Jesper,
> I have been troubled by the exact same behaviour and have solved it in
> the exact same way. In my opinion, it's a bug. Will you file a bug
> report against PDE or should I?
Done:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=63576
Best regards,
-Martin
>
> Best regards,
>
> Jesper
>
>
> Martin Lippert wrote:
>
>> Hi,
>>
>>> I have a plugin that has in addition to the normal source folder a
>>> ready-compiled jar file which is defined in the plugin.xml file as a
>>> runtime library (as well as the bundle classpath in the manifest.mf),
>>> too. This worked fine with m8 but I have problems with this setting
>>> with m9. Is this setting no longer supported or does it look like a bug?
>>
>>
>>
>> Solved the problem for myself, but the way it works is still somewhat
>> strange.
>>
>> I added the additional jar file (which is contributed by the same
>> plugin) to the extra classpath items of the build.properties. Then PDE
>> sets up the classpath correctly.
>>
>> If I tell PDE to update the classpath from the plugin.xml (or
>> manifest.mf) PDE does not add the jar library to the build path. This
>> does not seem to be correct behavior.
>>
>> Best regards,
>> -Martin
|
|
|
Powered by
FUDForum. Page generated in 0.07440 seconds
Home