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

Bug 195045

Summary:

Streamline TPTP installation from Eclipse Update Manager

Product:

z_Archived

Reporter:

Asaf Yaffe <asaf.yaffe>

Component:

TPTP

Assignee:

Joel Cayne <jcayne>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

jkubasta, stoian, xubing

Version:

unspecified

Keywords:

plan

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

closed460

Attachments:

Description	Flags
Screenshot	none

Description Asaf Yaffe

2007-07-01 04:53:03 EDT

Installing TPTP from the update manager is not a straight-forward process and may cause some confusion and grief to our end-users.

Here's a description of my experience:
1. I have downloaded the basic Eclipse "Java development" package and installed on my machine (Windows XP IA-32, single core).

2. I went to the Update Manager, selected the "Europa Discovery Site", expanded the "Test and Performance" category and was presented with a list of TPTP components (see attached screenshot). 

3. My intention was to install the 4.4 Java Profiler, so I selected only the "platform" component. I didn't think I will also need the "trace" component (which is confusingly marked with version 4.3 - see screenshot) until later, when I discovered that all profiling views are missing.

We must streamline the download process for the casual users. An "all-in-one" component, similar to the one we have in the TPTP download page is a possible solution.

Another issue here is that installing and using "cross-project" features, such as the Java Profiler (which requires both "platform" and "trace" projects) is complex. It requires two separate components, with no clear documentation or indication that both are required.

Comment 1 Asaf Yaffe

2007-07-01 04:53:26 EDT

Created attachment 72832 [details]
Screenshot

Comment 2 Joel Cayne

2008-03-12 17:02:56 EDT

The cause of (3) is probably due to a dependency requirement and would be similar to downloading only the Platform Runtime from the webpage.

To install an all-in-one download, the user would select the root level TPTP project and click on select required.

The numbers beside the features correspond to feature versions and may not match the release version. These numbers increase independently.

Comment 3 Asaf Yaffe

2008-03-13 02:58:10 EDT

(In reply to comment #2)
> The numbers beside the features correspond to feature versions and may not
> match the release version. These numbers increase independently.

Well, IMHO this is a bad practice. If feature versions do not match (on some level) to the release level, how do you expect our users to know which version to get? Would you like them to guess? Personally, if I want to download the "4.4" version of some plugin, I would never select a plugin labeled as "4.3"...

Comment 4 Joel Cayne

2008-03-13 08:37:13 EDT

Feature and Plug-in versions are set by the Version Numbering guidelines that all Eclipse developers should be following at http://wiki.eclipse.org/index.php/Version_Numbering.

Comment 5 Paul Slauenwhite

2009-06-30 14:19:07 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.