Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Plug-in Dependencies on 3.1 -> 3.2 RCP application
Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #461979] Fri, 19 January 2007 14:27 Go to next message
Nathan R. Yergler is currently offline Nathan R. YerglerFriend
Messages: 2
Registered: July 2009
Junior Member
I have a simple RCP application prototype that was initially developed
on Eclipse 3.1. When checking out the code with Eclipse 3.2, all of the
"org.eclipse" imports are marked as unresovable. For example,

import org.eclipse.core.runtime.IPlatformRunnable;

in Application.java. The "quick-fix" suggested is to add "Plug-in
Dependencies" to the build path. When I do that, it appears in the
build path, but no jars are in it. When I create an RCP application
from scratch using the new project wizard, the Plug-in Dependencies has
all the expected jars in it.

Is there some migration steps that need to be followed? Some lingering
cache files that were accidentally checked into Subversion and are
causing problems?

Thanks,

Nathan
Re: Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #461980 is a reply to message #461979] Fri, 19 January 2007 14:47 Go to previous messageGo to next message
Paul Webster is currently offline Paul WebsterFriend
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

Once you've added the dependencies in the plugin.xml/MANIFEST.MF
Dependencies tab, you can right click on your plugin and choose PDE
Tools>Update Classpath.

Later,
PW


Re: Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #461981 is a reply to message #461980] Fri, 19 January 2007 14:54 Go to previous messageGo to next message
Nathan R. Yergler is currently offline Nathan R. YerglerFriend
Messages: 2
Registered: July 2009
Junior Member
Paul Webster wrote:
> Once you've added the dependencies in the plugin.xml/MANIFEST.MF
> Dependencies tab, you can right click on your plugin and choose PDE
> Tools>Update Classpath.

Ah, that was it. Thanks, Paul!
Re: Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #462134 is a reply to message #461980] Tue, 23 January 2007 13:53 Go to previous messageGo to next message
John Sanda is currently offline John SandaFriend
Messages: 1
Registered: July 2009
Junior Member
I have a similar question/situation. I have a 3.1.2 RCP application with
which I want to start using the Eclipse 3.2.1 IDE for development. I
cannot upgrade the plug-in dependencies of the application to the 3.2.1
versions.

I copied my application's plug-in dependencies to
[eclipse_3.2.1_dir]/plugins. In my plug-in manifest, plugin.xml, I have
made sure that the required dependencies with correct versions are
present. I should also mention that my plugin.xml is built against the
3.0 DTD. I do not have a bundle manifest, MANFIEST.MF, defined.

When I launch my app from the IDE, I get a lot of exceptions saying that
I am missing 3.2 dependencies. When I open up the launch configuration
to make sure the right versions of required plug-ins are checked off,
the 3.1.2 plug-ins that I copied over do not show up in the list. I even
restarted eclipse after copying the plug-ins. Is there a way to get
those older versions of the plug-ins to show up?

For each of my app's plug-ins I also did PDE Tools > Update Classpath -
didn't help :-( Do I need to define a MANIFEST.MF? Am I wrong in
thinking that I can run a 3.1.2 RCP application in the 3.2.1 version of
the IDE?

Thanks.


Paul Webster wrote:
> Once you've added the dependencies in the plugin.xml/MANIFEST.MF
> Dependencies tab, you can right click on your plugin and choose PDE
> Tools>Update Classpath.
>
> Later,
> PW
Re: Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #462214 is a reply to message #462134] Wed, 24 January 2007 19:23 Go to previous messageGo to next message
Paul Webster is currently offline Paul WebsterFriend
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

OK, first of all as of 3.0 your plugins should have MANIFEST.MF files.
Yes, please create a MANIFEST ASAP, even if it's with your 3.1.2
environment.

But I'm curious, what are you trying to do. Is it you want to upgrade
your RCP app to run on 3.2.1, or you want to *develop* your 3.1.2 RCP
app using 3.2.1?

For the second one, you would go to Window>Preferences>PDE>Target
Platforms in your 3.2.1 workspace and create one that points at a 3.1.2
install.

Then your plugins will compile against 3.1.2 even though your eclipse is
3.2.1.

Later,
PW


Re: Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #462235 is a reply to message #462214] Thu, 25 January 2007 01:22 Go to previous messageGo to next message
John Sanda is currently offline John SandaFriend
Messages: 22
Registered: July 2009
Junior Member
To answer your questions, I am trying to do both. The current version of
the app is being upgraded to run on 3.2.1, and it will also be developed
on 3.2.1. There are earlier versions of the app that run on 3.1.2, and
are in maitenance mode; consequently, I only want to develop on 3.2.1
for these earlier versions of the app.

I mananged to figure it out. As suggested, for the earlier versions of
the app, I changed the target platform to point to my 3.1.2
installation. After doing this, the older plug-ins were visible, but I
still had a bunch of unresolved compiler errors. I starting importing
the 3.1.2 plug-ins into my workspace as binary plug-in projects, and
this resolved the compiler errors. Once I create my MANIFEST.MF, will I
still need to import the 3.1.2 plug-ins into my workspace?

- John

Paul Webster wrote:
> OK, first of all as of 3.0 your plugins should have MANIFEST.MF files.
> Yes, please create a MANIFEST ASAP, even if it's with your 3.1.2
> environment.
>
> But I'm curious, what are you trying to do. Is it you want to upgrade
> your RCP app to run on 3.2.1, or you want to *develop* your 3.1.2 RCP
> app using 3.2.1?

>
> For the second one, you would go to Window>Preferences>PDE>Target
> Platforms in your 3.2.1 workspace and create one that points at a 3.1.2
> install.
>
> Then your plugins will compile against 3.1.2 even though your eclipse is
> 3.2.1.
>
> Later,
> PW
Re: Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #462237 is a reply to message #462235] Thu, 25 January 2007 01:36 Go to previous messageGo to next message
John Sanda is currently offline John SandaFriend
Messages: 22
Registered: July 2009
Junior Member
I should have mentioned that one of the plug-in projects in my workspace
is JFace (including source), and it of course does have a MANIFEST.MF;
however, I was getting a lot of compiler errors in the jface project
until I started importing its dependencies into my workspace.


John Sanda wrote:
> To answer your questions, I am trying to do both. The current version of
> the app is being upgraded to run on 3.2.1, and it will also be developed
> on 3.2.1. There are earlier versions of the app that run on 3.1.2, and
> are in maitenance mode; consequently, I only want to develop on 3.2.1
> for these earlier versions of the app.
>
> I mananged to figure it out. As suggested, for the earlier versions of
> the app, I changed the target platform to point to my 3.1.2
> installation. After doing this, the older plug-ins were visible, but I
> still had a bunch of unresolved compiler errors. I starting importing
> the 3.1.2 plug-ins into my workspace as binary plug-in projects, and
> this resolved the compiler errors. Once I create my MANIFEST.MF, will I
> still need to import the 3.1.2 plug-ins into my workspace?
>
> - John
>
> Paul Webster wrote:
>> OK, first of all as of 3.0 your plugins should have MANIFEST.MF files.
>> Yes, please create a MANIFEST ASAP, even if it's with your 3.1.2
>> environment.
>>
>> But I'm curious, what are you trying to do. Is it you want to upgrade
>> your RCP app to run on 3.2.1, or you want to *develop* your 3.1.2 RCP
>> app using 3.2.1?
>
>>
>> For the second one, you would go to Window>Preferences>PDE>Target
>> Platforms in your 3.2.1 workspace and create one that points at a
>> 3.1.2 install.
>>
>> Then your plugins will compile against 3.1.2 even though your eclipse
>> is 3.2.1.
>>
>> Later,
>> PW
Re: Plug-in Dependencies on 3.1 -> 3.2 RCP application [message #462239 is a reply to message #462237] Thu, 25 January 2007 02:14 Go to previous message
John Sanda is currently offline John SandaFriend
Messages: 22
Registered: July 2009
Junior Member
I wanted to go through this process again so I started with a fresh
install of Eclipse 3.2.1. And this time around setting the target
platform was all I needed to do. I did not have import any plug-in
projects. I wonder if it was just a case of my workspace resources being
out of sync with the IDE before.

John Sanda wrote:
> I should have mentioned that one of the plug-in projects in my workspace
> is JFace (including source), and it of course does have a MANIFEST.MF;
> however, I was getting a lot of compiler errors in the jface project
> until I started importing its dependencies into my workspace.
>
>
> John Sanda wrote:
>> To answer your questions, I am trying to do both. The current version
>> of the app is being upgraded to run on 3.2.1, and it will also be
>> developed on 3.2.1. There are earlier versions of the app that run on
>> 3.1.2, and are in maitenance mode; consequently, I only want to
>> develop on 3.2.1 for these earlier versions of the app.
>>
>> I mananged to figure it out. As suggested, for the earlier versions of
>> the app, I changed the target platform to point to my 3.1.2
>> installation. After doing this, the older plug-ins were visible, but I
>> still had a bunch of unresolved compiler errors. I starting importing
>> the 3.1.2 plug-ins into my workspace as binary plug-in projects, and
>> this resolved the compiler errors. Once I create my MANIFEST.MF, will
>> I still need to import the 3.1.2 plug-ins into my workspace?
>>
>> - John
>>
>> Paul Webster wrote:
>>> OK, first of all as of 3.0 your plugins should have MANIFEST.MF
>>> files. Yes, please create a MANIFEST ASAP, even if it's with your
>>> 3.1.2 environment.
>>>
>>> But I'm curious, what are you trying to do. Is it you want to
>>> upgrade your RCP app to run on 3.2.1, or you want to *develop* your
>>> 3.1.2 RCP app using 3.2.1?
>>
>>>
>>> For the second one, you would go to Window>Preferences>PDE>Target
>>> Platforms in your 3.2.1 workspace and create one that points at a
>>> 3.1.2 install.
>>>
>>> Then your plugins will compile against 3.1.2 even though your eclipse
>>> is 3.2.1.
>>>
>>> Later,
>>> PW
Previous Topic:RCP -View with LWJGL example?
Next Topic:Export Product with ANT
Goto Forum:
  


Current Time: Wed Oct 16 02:29:09 GMT 2024

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

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

Back to the top