Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » jface packaging in 2.0 vs. 2.1
jface packaging in 2.0 vs. 2.1 [message #57580] Sat, 31 May 2003 11:15 Go to next message
Eclipse UserFriend
In Eclipse 2.0 the jface libraries are in the org.eclipse.ui plugin
but in eclipse 2.1.x the required plugin to use is org.eclipse.jface
This makes plugins requiring org.eclipse.jface not usable on 2.0
based platforms like WASD. This could be easily fixed by exporting
the jface dependency from org.eclipse.ui itself, so simply requiring
that would be sufficient to get to jface, and it will work both on 2.0
and 2.1.

Does this make sense, and/or is there another way to accomplish this?

Frank
Re: jface packaging in 2.0 vs. 2.1 [message #60204 is a reply to message #57580] Tue, 03 June 2003 07:51 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: daniel.megert.gmx.net

Frank Sauer wrote:

>In Eclipse 2.0 the jface libraries are in the org.eclipse.ui plugin
>but in eclipse 2.1.x the required plugin to use is org.eclipse.jface
>
Do you mean required in org.eclipse.ui itself or for clients?
- for org.eclipse.ui this is true but this is transparent for clients
since JFace is re-exported (see below).
- clients should reference org.eclipse.ui and not JFace unless they
really only want JFace and don't care to not be compatible to 2.0 stuff
(since there is not JFace plug-in in 2.0). Did you read somewhere that
JFace must be added as required plug-in?

>This could be easily fixed by exporting
>the jface dependency from org.eclipse.ui itself, so simply requiring
>that would be sufficient to get to jface, and it will work both on 2.0
>and 2.1.
>
Correct. That's exactly why in 2.1 JFace is exported by org.eclipse.ui.
From the plugin.xml:
<import plugin="org.eclipse.jface" export="true"/>

>Does this make sense, and/or is there another way to accomplish this?
>
2.1x plug-ins should not refer to JFace instead they should reference
org.eclipse.ui as in 2.0.

While developing the best thing to do is to reference other projects
instead of JARs. This is done automatically for you if you select a
plugin.xml and then select "Update Classpath..."

HTH
Dani
Re: jface packaging in 2.0 vs. 2.1 [message #60521 is a reply to message #60204] Tue, 03 June 2003 10:21 Go to previous message
Eclipse UserFriend
I did not add the jface plugin by choice, it either happened automatically
from your method described at the end, or because it did not work without
it. I've had people report that if they remove the requirement on jface, my
plugin
starts, but its preference pages don't work (on 2.0). But this sounds
hopeful and I'll try
to play with it some more.

Frank

"Daniel Megert" <daniel.megert@gmx.net> wrote in message
news:bbi250$en3$1@rogue.oti.com...
> Frank Sauer wrote:
>
> >In Eclipse 2.0 the jface libraries are in the org.eclipse.ui plugin
> >but in eclipse 2.1.x the required plugin to use is org.eclipse.jface
> >
> Do you mean required in org.eclipse.ui itself or for clients?
> - for org.eclipse.ui this is true but this is transparent for clients
> since JFace is re-exported (see below).
> - clients should reference org.eclipse.ui and not JFace unless they
> really only want JFace and don't care to not be compatible to 2.0 stuff
> (since there is not JFace plug-in in 2.0). Did you read somewhere that
> JFace must be added as required plug-in?
>
> >This could be easily fixed by exporting
> >the jface dependency from org.eclipse.ui itself, so simply requiring
> >that would be sufficient to get to jface, and it will work both on 2.0
> >and 2.1.
> >
> Correct. That's exactly why in 2.1 JFace is exported by org.eclipse.ui.
> From the plugin.xml:
> <import plugin="org.eclipse.jface" export="true"/>
>
> >Does this make sense, and/or is there another way to accomplish this?
> >
> 2.1x plug-ins should not refer to JFace instead they should reference
> org.eclipse.ui as in 2.0.
>
> While developing the best thing to do is to reference other projects
> instead of JARs. This is done automatically for you if you select a
> plugin.xml and then select "Update Classpath..."
>
> HTH
> Dani
>
Previous Topic:Launching Eclipse Programmatically
Next Topic:runtime problems with one plugin depending upon another plugin
Goto Forum:
  


Current Time: Sat Jun 07 20:49:01 EDT 2025

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

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

Back to the top