Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 108517

Summary:	Improve "Deploying the log parser" documentation
Product:	z_Archived	Reporter:	Dave Smith <smith>
Component:	TPTP	Assignee:	Dave Smith <smith>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P2
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	closed460
Bug Depends on:	106497
Bug Blocks:

Description Dave Smith

2005-08-31 16:24:12 EDT

Add the following hint to "4. Create a wrapper class for the parser" on 
the "Deploying the log parser" page.  It should be placed before the current 
Hint.

Hint: Ensure currentPlugin is set to the name of your plugin in the wrapper 
constructor.  For example, if your plugin is named myLogParser40, then
you should add the following line to your parser wrapper class constructor: 
currentPlugin = "myLogParser40";
If currentPlugin is not set correctly, the log parser will not execute properly 
when importing a log file.

Comment 1 Dave Smith

2005-08-31 16:49:07 EDT

Please target this to 4.1.  I think this is a P2 priority as it is documenting 
a common problem encountered by log parser writers.

Comment 2 Dave Smith

2005-09-01 10:35:43 EDT

Targetting this to 4.1 i2 and setting priority to P2.  Please change if you 
disagree.

Comment 3 Dave Smith

2005-10-10 01:50:34 EDT

With the changes for feature 50681 and bugzilla 106497, the suggested update 
for the "4. Create a wrapper class for the parser" section is now incorrect.  
The parser wrapper extension class does not require currentPlugin to be set in 
the constructor.

As a result, I added more information about when a parser wrapper extension 
class is required.

Comment 4 Dave Smith

2005-10-10 01:52:18 EDT

Fix to org.eclipse.tptp.monitoring.doc.user/tasks/tconfiguremanifestfile.html 
committed to Head CVS.

Comment 5 Paul Slauenwhite

2009-06-30 08:09:03 EDT

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.