Summary: | Logging sample project names should not include Hyades | ||
---|---|---|---|
Product: | z_Archived | Reporter: | Dave Smith <smith> |
Component: | TPTP | Assignee: | jkubasta |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | CC: | nmehrega, paulslau |
Version: | unspecified | Keywords: | Documentation |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | housecleaned460 closed460 | ||
Bug Depends on: | |||
Bug Blocks: | 96029 |
Description
Dave Smith
2005-05-19 16:35:46 EDT
Target this to 4.1 as it is not a high priority and it affects the readme documentation that is frozen for 4.0. Bugzilla 96029 was created to change the sample readme's to reflect the changes included in this bugzilla. *** Bug 102012 has been marked as a duplicate of this bug. *** *** Bug 103685 has been marked as a duplicate of this bug. *** The TPTP logging examples contain references to Hyades in the UI (e.g. wizard panes) and default settings (e.g. newly created project). Also note that the readme.html files of some samples still refer to Hyades Correcting the target. Deferring to i2 because it could not be contained in i1 For the TPTP-4.1.0-200509160100 driver, the readme.html file of the JSR-047 sample seems to be updated with the new project name ("LoggingJava14Project"), but the sample seems to still use the old project name (i.e. "HyadesLoggingJava14Project"). Deferring this to 4.1 i3 as approved by Sri. Deferring to 4.2. Not a stop ship issue and cannot be contained in 4.1. The name of the Logging Agent contain the 'Hyades' prefix which also needs to be changed. The Logging Agent names should be changed in the readme as well as the constant in the sample class (see defect description). Targetting to 4.2 i3 Deferring to 4.3 as it is not stop ship and cannot be contained in 4.2. Dropping the priority to P2 as it cannot likely be contained in TPTP 4.3. Cannot be contained in 4.3. Deferring to 4.4. Reassigning defects to current component owner. Reassigning to new component lead. 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. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. 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 originator of this enhancement/defect has an inactive Bugzilla account 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. 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 the originator of this enhancement/defect has an inactive Bugzilla account 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. |