| Bundle-ClassPath not processed in 3.5RC1 [message #62269] |
Wed, 20 May 2009 07:39  |
Eclipse User |
|
|
|
Before I file this as a bug, just a quick cross-reference.
I've added a jar to the plug-in project, and then declared that jar in
the 'Classpath' area under the 'Runtime' tab of the Manifest editor.
Yet, the 'Exported Packages' area remains disabled. I cannot 'Add,
Remove, ...'. The buttons are disabled. I've tried different jars from
different sources to check if the problem is associated with the package
itself, but the problems remains.
Any feedback on this?
Best,
Dann
|
|
|
|
|
| Re: Bundle-ClassPath not processed in 3.5RC1 [message #62464 is a reply to message #62317] |
Thu, 21 May 2009 09:28  |
| Eclipse User |
|
|
|
I have found the way to reproduce this, and contrary to my previous
statement, those exact steps also cause the same problem in 3.5M7; I'll
file a bug on this one.
Dann Martens wrote:
> Repeated the steps with 3.5M7 and there it still works.
>
> If someone from the PDE team gives me a nudge, I'll enter this as a bug.
>
> Best regards,
> Dann
>
> Dann Martens wrote:
>> ... I forgot to add this:
>>
>> Manually adding the corresponding 'Export-Package' header to the
>> Manifest, with the expected packages yields the error message that
>> this package does not exist in this plug-in.
|
|
|
|
| Re: Bundle-ClassPath not processed in 3.5RC1 [message #597667 is a reply to message #62293] |
Wed, 20 May 2009 08:17 |
| Eclipse User |
|
|
|
Repeated the steps with 3.5M7 and there it still works.
If someone from the PDE team gives me a nudge, I'll enter this as a bug.
Best regards,
Dann
Dann Martens wrote:
> ... I forgot to add this:
>
> Manually adding the corresponding 'Export-Package' header to the
> Manifest, with the expected packages yields the error message that this
> package does not exist in this plug-in.
|
|
|
| Re: Bundle-ClassPath not processed in 3.5RC1 [message #597711 is a reply to message #62317] |
Thu, 21 May 2009 09:28 |
| Eclipse User |
|
|
|
I have found the way to reproduce this, and contrary to my previous
statement, those exact steps also cause the same problem in 3.5M7; I'll
file a bug on this one.
Dann Martens wrote:
> Repeated the steps with 3.5M7 and there it still works.
>
> If someone from the PDE team gives me a nudge, I'll enter this as a bug.
>
> Best regards,
> Dann
>
> Dann Martens wrote:
>> ... I forgot to add this:
>>
>> Manually adding the corresponding 'Export-Package' header to the
>> Manifest, with the expected packages yields the error message that
>> this package does not exist in this plug-in.
|
|
|
Powered by
FUDForum. Page generated in 0.08886 seconds
Home