Community
Participate
Working Groups
In order to capture information about what context particular events belong to, we require that a new trace element be added. It would appear in the trace as: <contextDef name="mycontextname" id="mycontextid_number"/> We should then be able to reference it at least from classDef and methodEntry elements using a contextRefId attribute. For example: <methodEntry ... contextRefId="mycontextid_number" ... /> <classDef ... contextRefId="mycontextid_number" ... /> (where ... are standard methodEntry/classDef attributes).
Created attachment 35624 [details] a more detailed example of how ContextDef would be used
Please also add support for this class in the filter engine. I'm sure it will be needed.
Batch update of all TPTP platform enhancements that are not part of 4.2 approved plan. Set version to "future" and target milestone to "--".
Reassigning due to Marius' absence.
Impl of this defect is directly related to bug #110966. Raising into 4.4 as 110966 was targetted to this release.
Reassigning due to Ruth's leave of absence. Added Matt to the CC.
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 the originator of this enhancement/defect has an inactive Bugzilla account and it may be no longer relevant. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
