Ah I see. Yep, that would work great.
Roy
Eugene Kuleshov wrote:
>
> The point is that, they won't be embedded anymore.
>
> regards,
> Eugene
>
>
> Roy Paterson wrote:
>> Even if they're OSGi bundles I think you would still need to unpack
>> them if they have embedded jars.
>>
>> Eugene Kuleshov wrote:
>>>
>>> In this case it is probably better to break subclipse.core plugin
>>> into core and two client plugins (javahl and svnkit) and only unpack
>>> the clients or better make them OSGi bundles, which would only take
>>> to change manifest file in the jar.
>>>
>>> regards,
>>> Eugene
>>>
>>>
>>> Roy Paterson wrote:
>>>> :-) I have done that and it works fine - but it's irritating - all
>>>> the other plugins I depend on work fine with the PDE in the normal
>>>> way without having to build them from source.
>>>>
>>>> I agree that this is obviously a limitation in the PDE since it
>>>> works in the runtime, but I think it's good practice at runtime to
>>>> unpack the plugin jar as well. I think I remember hearing that
>>>> there were performance issues with the Eclipse classloader loading
>>>> code from jars-within-jars, and this was one of the main reasons
>>>> (besides backwards compatibility) that they made the "unpack" option
>>>> configurable.
>>>>
>>>> Regards,
>>>> Roy
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Wed Jan 24 20:08:45 2007