Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Runtimes » org.eclipse.core.runtime.compatibility.registry
org.eclipse.core.runtime.compatibility.registry [message #468638] Mon, 22 June 2009 14:02 Go to next message
Paul Warren is currently offline Paul WarrenFriend
Messages: 34
Registered: July 2009
Member
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

Report message to a moderator

Re: org.eclipse.core.runtime.compatibility.registry [message #468640 is a reply to message #468638] Mon, 22 June 2009 17:36 Go to previous message
Oleg Besedin is currently offline Oleg BesedinFriend
Messages: 41
Registered: July 2009
Member
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
>
>
>
>
>

Report message to a moderator

Re: org.eclipse.core.runtime.compatibility.registry [message #572266 is a reply to message #468638] Mon, 22 June 2009 17:36 Go to previous message
Oleg Besedin is currently offline Oleg BesedinFriend
Messages: 41
Registered: July 2009
Member
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
>
>
>
>
>

Report message to a moderator

Previous Topic:org.eclipse.core.runtime.compatibility.registry
Next Topic:PDE API Tools
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Apr 19 00:23:50 GMT 2024

Powered by FUDForum. Page generated in 0.01999 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly