Re: [eclipse-dev] comment on draft 3.0 plan - need better upgrade option

[Mazz Golf <mazzgolf@xxxxxxxxx>]

> Delete everything ... except workspace directory

This isn't a good thing to rely upon though - we
should not assume future versions of Eclipse will have
compatible metadata (e.g. the .metadata directory
contents).

One other problem I had when I moved from 2.0 to 2.1
(while keeping the old workspace/.metadata directory)
is the format of the .externalToolBuilders directory
seemed to have changed; I had to delete it and
recreate the definition in 2.1.  Little things like
that is what I'm afraid of losing when I upgrade.

I just think it would be a better design to explicitly
provide an upgrade path through an installation tool. 
Or, at the very least, have an installation doc or
README on how to successfully upgrade and not lose
anything.  As it stands, even that trick of keeping
the workspace or .metadata directory wasn't documented
well (if at all; I think I just guessed at that when I
tried it).

John

--- Vjekoslav Nesek <vnesek@xxxxxxxxx> wrote:
> Well YMMV but here is what works quite good 
> for me (Eclipse installation is in C:\eclipse):
> 
> 1. Backup C:\eclipse\workspace
> 2. Delete everything from C:\eclipse except
>    workspace directory
> 3. Unpack new version in C:\eclipse (actually
>    into C:\ as windows .zip already includes
>    eclipse directory)
> 
> This worked okay between 1.0 and 2.0, 2.1RCx and
> 2.1 final. All preferences (I don't tend to edit
> much except perhaps editor fonts and such) were
> saved as well as templates. However when you first 
> time start a new version, workspace will be
> upgraded, so if you don't like new version you
> will have to resort to bakcup.
> 
> BR,
> Vjeko
> 
> 
> --- Mazz Golf <mazzgolf@xxxxxxxxx> wrote:
> > [resending - sorry if duplicates are received]
> > 
> > I have a comment on the current Draft 3.0 plan.
> > 
> > IMO, Eclipse needs a better upgrade option.  As it
> > stands, there is no way to upgrade a currently
> > installed Eclipse environment from one release to
> > another (e.g. I have 2.0 installed but want to
> move
> > to
> > 2.1).
> > 
> > The Eclipse configuration Properties can be
> imported
> > and exported, but not all of the configuration
> > settings get saved (like templates and custom
> plugin
> > configuration).  And you still have to manually
> > import
> > all of your projects; history gets lost, etc. etc.
> > 
> > Has anyone considered addressing this?  I don't
> see
> > anything like this even listed in the "rejected"
> > category; so either this was never brought up or
> my
> > understanding on how to upgrade an installation is
> > wrong ;-)
> > 
> > John Mazz
> > 
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Calendar - Free online calendar with sync
> to
> > Outlook(TM).
> > http://calendar.yahoo.com
> > _______________________________________________
> > eclipse-dev mailing list
> > eclipse-dev@xxxxxxxxxxx
> >
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Calendar - Free online calendar with sync to
> Outlook(TM).
> http://calendar.yahoo.com
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com