| org.eclipse.core.runtime.compatibility.registry [message #468638] |
Mon, 22 June 2009 10:02  |
Eclipse User |
|
|
|
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
|
|
|
| Re: org.eclipse.core.runtime.compatibility.registry [message #468640 is a reply to message #468638] |
Mon, 22 June 2009 13:36  |
| Eclipse User |
|
|
|
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@emc.com> wrote in message
news:h1o2su$p3$1@build.eclipse.org...
> 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
>
>
>
>
>
|
|
|
| Re: org.eclipse.core.runtime.compatibility.registry [message #572266 is a reply to message #468638] |
Mon, 22 June 2009 13:36 |
| Eclipse User |
|
|
|
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@emc.com> wrote in message
news:h1o2su$p3$1@build.eclipse.org...
> 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
>
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.07713 seconds
Home