[news.eclipse.rt] Re: org.eclipse.core.runtime.compatibility.registry

["Oleg Besedin" <obesedin@xxxxxxxxxx>]

This fragment uses a classpath trick to replace some of the class files in 
its host. That only work with unzipped bundles.

I'd say if the application needs the 
org.eclipse.core.runtime.compatibility.registry fragment, then that fragment 
has to be supplied as a folder. However, not all bundles need it, so if you 
are dealing with a "closed" set of plugins, then you can test/update those 
plugins to the point where they don't need compatibility fragment.

Sincerely,
Oleg Besedin

"Paul Warren" <warren_paul@xxxxxxx> wrote in message 
news:h1o2su$p3$1@xxxxxxxxxxxxxxxxxxxx
> Hi Folks,
>
> I've done a bit of googling but cant find any specific 
> reasons/justifications for this.
>
> I'm trying to work out why org.eclipse.core.runtime.compatibility.registry 
> is deployed as a folder as opposed to a jar.
>
> Some internal customers for a servletbridge-based product are asking me if 
> we can deploy this frgament as a jar.  Is this possible or is there a 
> reason why it is unpacked to a folder?
>
> Many thanks
> _Paul
>
>
>
>
>