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

Bug 161772

Summary:	Redesign Static Instrumentation experience
Product:	z_Archived	Reporter:	Ashish Patel <ashishp>
Component:	TPTP	Assignee:	Ashish Patel <ashishp>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	nmehrega
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	closed471
Bug Depends on:
Bug Blocks:	173202

Description Ashish Patel

2006-10-20 15:05:45 EDT

1) The current static instrumentation UI (right click on a .probe file and select Instrument->static instrument) says that you can instrument .class, .jar, .war, .ear files.  This is incorrect.  I can't instrument .war and .ear files - right now I have to rename the ear and war to a jar and then instrument and rename back to ear or war.  
a) We need support to instrument WAR and EAR (in addition to JARs).
b) We need a better experience for static instrumentation.

2) The whole concept of having the user find a probe and use it for instrumentation - requires that the user knows where the probe is located on the file system and the purpose of that probe.  I'd rather see the probe be contributed via some extension point and users can pick from a list the probes they want to use for instrumentation.

3) remove the need for right clicking on a probe or Jar/class file.  This doesn't seem intuitive for a user.  I put some ideas into https://bugs.eclipse.org/bugs/show_bug.cgi?id=135961 which I think can help fulfill this piece. (135961  - Statically instrument an application without having to import probekit probes into the workspace)

4) The UI needs redesign so its consistent with eclipse dialogs.  Also the trees in the dialogs need to be filtered, or provide filtering.  I'd rather see UI like the "Build Path" configuration window in Java projects.

This work is needed to make future products work nicely with a good experience.  In addition, this is need to make the immediate work in the ARM tech preview easier to instrument statically - there are companies already trying to use this and its been utter chaos with manual steps and hacks lately.  

I think this needs to be top priority for fixing TPTP 4.4.

Comment 1 Valentina Popescu

2007-01-15 12:15:06 EST

Not in plan for 4.4; Moving target to future

Comment 2 Paul Slauenwhite

2009-06-30 06:41:33 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).

Comment 3 Paul Slauenwhite

2009-06-30 06:48:40 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).

Comment 4 Kathy Chan

2010-11-18 18:54:49 EST

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.