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 09:27  |
Eclipse User |
|
|
|
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 #462235 is a reply to message #462214] |
Wed, 24 January 2007 20:22   |
Eclipse User |
|
|
|
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] |
Wed, 24 January 2007 20:36   |
Eclipse User |
|
|
|
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] |
Wed, 24 January 2007 21:14  |
Eclipse User |
|
|
|
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
|
|
|
Goto Forum:
Current Time: Thu Jun 19 10:12:37 EDT 2025
Powered by FUDForum. Page generated in 0.27667 seconds
|