Community
Participate
Working Groups
Separate enhancement required in Bug 196744 (enhancement: JVMTI standalone profiling data collection) Standalone profiling execution requires to put complex options sequence for JVM. Though number of options isn't very big, user often are become confused about them. Such things as options order, separators between them and their combined usage cannot be caught and remembered easily, user often should refer to documentation. To avoid such bad user experience console wizard for JVM TI profiler configuration is proposed. Wizard can contain number of steps on which it ask users to select one of available option with some additional information about it or input string (paths to JRE or AC) and then put it in correct place.
AG approved for 4.5 given the following conditions/comments: -Do you have the resource/time to complete the design/code/test/documentation/build in I6 development (target: March 21)? Implementation, test, and documentation sizing seem low. -For documentation, we will need something equivalent to the Agent Controller's getting_started.html for both Linux and Windows. In addition, we should provide a reference in our product documentation (Help >> Help Contents). -What do you mean by the 'text mode' for the UI? Will this be a GUI that has simple text/combo/radio inputs? If so, will it be SWT or Swing? -Why do you need to know the operation system for which profiling configured? -Each of these configuration options should have a small textual explanation. -Change the default filter file name from ilters.txt to filters.txt. -Should thread profiling be the default. I would assume execution statistics would be more relevant to first time users. -When the user inputs filters, the wizard should provide text inputs for class and method patterns and a selection for the mode (e.g. include/exclude).
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.
