RE: [eclipse-dev] comment on draft 3.0 plan

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

RE: [eclipse-dev] comment on draft 3.0 plan - need better upgrade options

From: Eric McIntyre <EMcIntyre@xxxxxxxxxxxxxxxxx>
Date: Tue, 3 Jun 2003 12:22:15 -0700
Delivered-to: eclipse-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/eclipse-dev/>
List-help: <mailto:eclipse-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=unsubscribe>

Title: RE: [eclipse-dev] comment on draft 3.0 plan - need better upgrade options

> But, I still remember my .externalTools directory not
> working when I did this (I think it was when I moved
> from 2.0 MP4 to 2.1, but I can't remember). Just
> copying the workspace over didn't work.

We've been using Eclipse since 1.0, and have upgraded many times. I've found that my coworkers usually had problems with upgrading when they did so infrequently, such as 2.0 -> 2.1 M5. When I kept current with the milestones and releases, upgrading went smoothly. For that matter, whenever I rolled back to a previous version because of instabilities with the build, that went smoothly, too. In other words, try upgrading incrementally to avoid compatibility problems.

Eric

Prev by Date: Re: [eclipse-dev] SWT Markup should be in the 3.0 plan
Next by Date: Re: [eclipse-dev] SWT Markup should be in the 3.0 plan
Previous by thread: [eclipse-dev] Setting global vm args in releng automated test framework
Next by thread: [eclipse-dev] [eclipse-build]Build N20030604 (Timestamp: 200306040010):Compile errors in build
Index(es):
- Date
- Thread

Breadcrumbs