Home » Eclipse Projects » Rich Client Platform (RCP) » Plug-in Dependencies on 3.1 -> 3.2 RCP application
| | | | |
| 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   |
 John Sanda
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 |
John Sanda
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 |
John Sanda
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
|
|
|
Goto Forum:
Current Time: Sun Oct 06 17:02:10 GMT 2024
Powered by FUDForum. Page generated in 0.06753 seconds |
] 
Search
Help
Register
Login
Home
