installing 3.2 using Update Manager [message #159623] |
Wed, 05 July 2006 10:52  |
Eclipse User |
|
|
|
Originally posted by: pavel.sapozhnikov.gmail.com
Hi can anybody help me with installing 3.2 using Update Manager. How do I
do it? I ran update manager and I did both of the choices and I didn't get
any results for 3.2 can you guys tell me how to do it.
Thanks.
|
|
|
|
|
|
|
Re: installing 3.2 using Update Manager [message #159674 is a reply to message #159667] |
Wed, 05 July 2006 14:24   |
Eclipse User |
|
|
|
Originally posted by: hendrik_maryns.despammed.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pavel Sapozhnikov schreef:
> Hendrik Maryns wrote:
> Pavel Sapozhnikov schreef:
>>>> Jeff Myers wrote:
>>>>> Pavel,
>>>>>
>>>>> You can not update major Eclipse versions via the Update Manager. You
>>>>> need to do a clean install of base Eclipse 3.2 to a new directory,
>>>>> then you can use Update Manager to add additional plug-ins. See
>>>>> http://www.eclipse.org/callisto/ for details.
>>>>>
>>>>> Hope this helps,
>>>>> - Jeff
>>>> Hi Jeff. So lets say I do just a clean install which is fine. I am using
>>>> pydev plugin for eclipse and I already have a workspace and all that
>>>> stuff and also I dont want to loose my preferences that is my
>>>> configuration such as coloring of the code etc. How would I go about not
>>>> losing all that.
>
> It is recommended to first take a copy of you workspace, install the new
> Eclipse *next to* the old one, point the new Eclipse to the copy, and
> keep the old copy at hand for when something goes wrong. Once
> everything is going fine, you can delete the old copy and the old
> Eclipse.
> What do you mean when you say "next to". Also all my plug-ins will be
> gone. So what do I do about that. Just install the plug-ins again?
I mean: leave the old Eclipse where it is, and install the new one in a
different folder (or, if you want to have a specific name for the
folder, rename the old one first). Yes, you plug-ins will be gone, you
will have to reinstall them too. I find this a PITA when upgrading
Eclipse, they should take an example from Mozilla. However, the update
manager now comes with some predefined sites which contain much of the
most-wanted plugins.
Otherwise, you can export your update sites in the old eclipse, and
import them in the new one (see the update sites window).
H.
- --
Hendrik Maryns
==================
http://aouw.org
Ask smart questions, get good answers:
http://www.catb.org/~esr/faqs/smart-questions.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFErAPGe+7xMGD3itQRAqvfAJ4xhHcNdci3Y4i9um02fsOMz1KwTgCe I0xm
923aL/56AZ+hnFdzBmQOcYM=
=aA1b
-----END PGP SIGNATURE-----
|
|
|
Re: installing 3.2 using Update Manager [message #159691 is a reply to message #159659] |
Wed, 05 July 2006 17:16  |
Eclipse User |
|
|
|
Originally posted by: jeff.dilacero.org
> It is recommended to first take a copy of you workspace
[..]
I think the Eclipse website really needs to have prominent instructions
on how to upgrade. I made this suggestion a few days ago but got no
feedback. Should I file a bug/feature request somewhere?
-Jeff
|
|
|
Powered by
FUDForum. Page generated in 0.09711 seconds