Community
Participate
Working Groups
Create export wizard for instrumenting a JAR/WAR/EAR. The static instrumentation use case allows a user to export a compiled version of the user’s Java program, and instrument the export bundle. For example, a WAR file can be exported for a servlet-based application and instrumented automatically. The following is a brief outline of the user’s actions to leverage static instrumentation in the BtM: 1) From the Eclipse menu select: File -> Export 2) Select a JAR, WAR, EAR file. 3) Select the probes to instrument with and filters to apply. 4) Select where to export the instrumented version of the file to. 5) User can deploy archive into the application container of choice. TPTP related: - 135961 enh - Statically instrument an application without having to im... - 161772 enh - Redesign Static Instrumentation experience - 126432 enh - [Probekit UI] Get rid of the Filter tab for the 'Probe' p...
deferring - this involves UI and string changes.
1) From the Eclipse menu select: File -> Export 2) Select a project/class files 3) Select whether we are using ARM (probes or aspects), JMX, or CBE. The list of probes should be loaded from the workspace and the extension point to which probes are contributed that aren't currently imported into the workspace. Same thing with aspects. 4) Select where to export the instrumented version of the file to. (and any options like compressing the export archive, including the source code, etc) 5) User can deploy archive into the application container of choice. If ARM is selected, the various ARM and TPTP dependencies should be either included in the archive or proper instructions should be presented to the user as to what should be put onto the class path. Preferably a single jar is made with all the dependencies. Also: a use case needs to be developed for instrumenting an existing JAR, WAR, EAR file. The Instrument -> Static (right click on the JAR or class file or probe file) should be removed as well) since the wizard should be used instead. Same with "Add/Remove BtM instrumentation support" - it doesn't work and I don't see the point of it.
Assigning to Paul for implementation.
This is an enh
Additions requirements, generated from https://bugs.eclipse.org/bugs/show_bug.cgi?id=163857 Include/Export the runtime dependencies with the instrumented JAR/WAR/EAR. This can be achieved by creating a project that references the single dependency file which can be reused across code projects that require to be run with instrumentation.
reassigning - address in future release if the requirement is there.
Reassign to Richard who is the new owner of the component.
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).
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.
