Community
Participate
Working Groups
The Foundation has asked TPTP to divide its online help into two categories: doc for users (developers who use TPTP to test & profile) and doc for consumers (extenders of TPTP). Both types of documentation remain in the plug-in format, but the consumer documentation should be shipped only in the SDK. The user documentation should remain in the binary production driver of TPTP. The org.eclipse.platform/jdt plug-ins have chosen a naming convention of "doc.user" and "doc.isv". This enhancement is for the Project to analyze its online help documentation, categorize it according to its target audience, and refactor the documentation into two plug-ins.
proposed to be planned for 4.2 but no resources are available (helpwanted keyword added)
Target set to 4.2
Investigation shows that there is no existing trace doc user plug-in (it's all in platform), hence there is no work for the Trace.Doc component. Closing.
Reopening based on feedback. It has been requested that the following examples be removed from the monitoring project and into the trace project: - Column Extension Sample - Context Language - Export Viewer Generator - Filter Type Sample This means that a "trace.doc.isv" plug-in and a "trace.examples.isv" plug-in need to be created in the trace project, and that the ISV features will need to be updated to include them. I suspect that this means that we might need a new trace feature?
Ruth, After reviewing with Dave, the following 3 should be considered a platform isv example - Context Language - Export Viewer Generator - Filter Type Sample Only the - Column Extension Sample - fits under trace isv example. Thanks
Two new plug-ins, org.eclipse.tptp.trace.doc.isv and org.eclipse.tptp.trace.examples.isv have been created. The other three examples were moved to platform ISV as discussed.
Reopening for the refactoring of the test suites.
Done.
Moving bugs from Trace.Doc to Platform.Doc because Trace.Doc will be removed.
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.