Bug 31910 - Eclipse upgrade instructions
Summary: Eclipse upgrade instructions
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Doc (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1   Edit
Assignee: Platform-Doc-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-14 15:19 EST by Ron Baldwin CLA
Modified: 2005-05-19 17:14 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Baldwin CLA 2003-02-14 15:19:38 EST 
From the traffic on the newsgroup, there should probably be some easily
accessable instructions on how to upgrade Eclipse.  Ideally it should cover
integration, milestone and release instructions.

I would propose:
1. A FAQ entry
2. A Readme that is both included in the root directory of downloaded archive
files, and linked to from the download page.
Comment 1 Alex CLA 2003-02-15 01:20:57 EST 
A modest proposal: 3. An automatic upgrade path via Update Manager (documented 
in FAQ if available now)
Comment 2 Ron Baldwin CLA 2003-02-18 03:20:54 EST 
Maybe obvious, but it should also cover techniques like putting your 3rd-party
plug-ins in a separate directory structure and using the ECLIPSE_HOME/links
directory.
Comment 3 Oleg Shteynbuk CLA 2003-02-18 13:26:40 EST 
http://home.nyc.rr.com/olegs/eclipse/antscript/readme.htm  
could be a starting point.

"What is the Right Way to Update?" section describe how to put 3rd-party
plug-ins in a separate directory and links directory among other things.
Comment 4 Nick Edgar CLA 2003-03-13 16:54:09 EST 
We will describe how to upgrade in the README and in the FAQ for 2.1.
Comment 5 John Arthorne CLA 2003-03-26 14:37:59 EST 
Added new section to README and platform user doc.
Comment 6 John Arthorne CLA 2005-05-19 17:14:04 EDT 
Marking this one fixed.  Upgrade instructions are in the readme and in the user
documentation.