Upgrading Eclipse from 2.1 to 2.1.1 [message #74592] |
Fri, 11 July 2003 09:03  |
Eclipse User |
|
|
|
Hi,
I have been comiling my Java programs in Eclipse 2.1.0 Build id:
200303071024
I recently downloaded Eclipse 2.1.1 Build id: 200306271545.
I wish to upgrade to 2.1.1.
I know it is as simple as extracting the 2.1.1 zip to a folder and then
migrating the 2.1.0 workspace to 2.1.1
(else create the projects in the 2.1.1 workspace, one by one)
I did some exploration, and found simple extracting eclipse 2.1.1 ON TOP
OF 2.1.0 will NOT overwrite ALL plugins and features of eclipse 2.1.0 as
the names differ.
For e.g.
In .\features of 2.1.0 we have "org.eclipse.jdt.source_2.1.0" and in
In .\features of 2.1.1 we have "org.eclipse.jdt.source_2.1.1"
Similarly,
In .\plugins of 2.1.0 we have "org.eclipse.jdt.core_2.1.0" and in
In .\plugins of 2.1.1 we have "org.eclipse.jdt.core_2.1.1"
The contents of similar named folders however have the same name (and will
of course be upgraded - I guess)
and so on with many other folders
Where does Eclipse store the info on which plugin/ feature to use?
I mean use "org.eclipse.jdt.source_2.1.1" and not
"org.eclipse.jdt.source_2.1.0"
etc..
I expect and know an answer, like,
"One can extract ver 2.1.1 on top of 2.1.0 (selecting overwrite existing
files if any).
Eclipse when started will prompt to apply the upgrade or to remove it"
But that aside I still would like to know where Eclipse keeps info "on
what feature/ plugin" to use.
Just for kicks.
rgds
g1
|
|
|
|
|
|
Re: Upgrading Eclipse from 2.1 to 2.1.1 [message #74797 is a reply to message #74646] |
Fri, 11 July 2003 12:05  |
Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
Eric Rizzo wrote:
> Jeevan S wrote:
>
>> Hi,
>>
>> I have been comiling my Java programs in Eclipse 2.1.0 Build id:
>> 200303071024
>> I recently downloaded Eclipse 2.1.1 Build id: 200306271545.
>>
>> I wish to upgrade to 2.1.1.
>> I know it is as simple as extracting the 2.1.1 zip to a folder and then
>> migrating the 2.1.0 workspace to 2.1.1
>> (else create the projects in the 2.1.1 workspace, one by one)
>
>
> Why not just use the built-in Update Manager? It will detect,
> download, and install all available updates for Eclipse.
Because the Update Manager does not support to update from an
integration build to a full version. It's purpose is to update from one
official final versions to a new one, e.g. original 2.0 to 2.1. Note
that in above scenario the Update Manager will do some updating but the
result might be surprising.
Dani
|
|
|
Powered by
FUDForum. Page generated in 0.03635 seconds