Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 460563

Summary:	Nature of the installer workflow and permanence of artifacts
Product:	[Tools] Oomph	Reporter:	Wayne Beaton <wayne.beaton>
Component:	Setup	Assignee:	Eike Stepper <stepper>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, julian.enoch
Version:	1.1.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	459836

Description Wayne Beaton

2015-02-22 23:17:22 EST

The intended workflow for the installer isn't clear to me.

On Windows, the installer extracts the Oomph RCP app to a directory selected by the user. Is the intention that this directory is permanent or should it be considered temporary for the duration of the installation.

More directly, if the user wants to run the installer again, do we expect that they'll double click on the installer exe or will they launch the eclipse.exe in the RCP app?

In general, I expect an installer to extract something to a "temporary" directory that is destroyed when installation is complete. To do otherwise is a little confusing and may potentially be regarded as sloppy by the user.

Here's what I think the average user would expect to happen:

1) Launch the installer exe
2) Automatically extract to a temporary directory (potentially after asking permission to do so)
3) Automatically update the extracted installer as necessary
4) Step the user through the installation wizard and install the product with optional launch
5) Clean up the temporary files.

Expecting to keep the Oomph installer around is, IMHO, a little too meta for the average user.

Thoughts?

Comment 1 Eike Stepper

2015-04-03 04:50:28 EDT

This new workflow is now in place, see bug 459589.