Bug 558223 - Upgrading Eclipse chapter very vague
Summary: Upgrading Eclipse chapter very vague
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Doc (show other bugs)
Version: 4.13   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Doc-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-11 08:24 EST by David Balažic CLA
Modified: 2021-12-07 03:51 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Balažic CLA 2019-12-11 08:24:53 EST
At https://help.eclipse.org/2019-09/topic/org.eclipse.platform.doc.user/tasks/tasks-2.htm?cp=0_3_1
the chapter "Upgrading Eclipse" is very vague on the scenario not using the -data argument.

For the case it is used, there are clear instructions, I quote:

Using the "-data" argument

If you were previously using the "-data" argument to start Eclipse, your upgrade path is much easier:

    Install the new version of Eclipse in a new location, separate from any old version of Eclipse.
    Start this new version of Eclipse, using the "-data" command line argument to point to your old workspace location.

See the example in the previous section for an illustration.
-------------------end quote-----------

For the other case, only this sentence is written (and a lot of text about what workspaces are, what are the default locations etc... not much related to upgrading workspaces):

To load a workspace created using 3.0 or earlier, just point to the old workspace directory using the workspace chooser, whether it's under the old install directory or elsewhere.

So the points are:
 - the case not using -data should have it own titled section
 - the case of loading a workspace created with newer than 3.0 should be described
Comment 1 Eclipse Genie CLA 2021-12-06 18:46:36 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 David Balažic CLA 2021-12-07 03:51:33 EST
the problem still occurs, same as described in first comment