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

Bug 369393

Summary: Unable to export CDT user defined error parser
Product: [Tools] CDT Reporter: gregory tauveron <gregory.tauveron>
Component: cdt-buildAssignee: cdt-build-inbox <cdt-build-inbox>
Status: NEW --- QA Contact: Jonah Graham <jonah>
Severity: normal    
Priority: P3 CC: aegges, cdtdoug, gregory.tauveron, GurceIsikyildiz, nyssen, sorenenemark
Version: 8.0   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
Whiteboard:

Description gregory tauveron CLA 2012-01-23 09:57:21 EST
Build Identifier: M20110909-1335

When I define and add an error parser for my makefile project and then export my properties, I couldn't import it in my new workspace. Every custom parameters are imported but error parser are not.

Reproducible: Always

Steps to Reproduce:
1.Go to preferences then edit error parsers
2.Add (an error parser)
3.Name is BOOST Test Error Parser
4.Add (a parser option)
5.Set the parser like this
Severity: Error
Pattern: (.*)\((\d*)\): (error in .*)
File: $1
Line: $2
Description: $3
6.Apply then OK
7.Select File/Export/General/Preferences
8.Select Export All and set the file name to export data to my_eclipse_preferences.epf
9.Clic finish
10.Import that preference (import all) file into an other workspace and restart. I do not have my error parser imported.
Comment 1 Andrew Gvozdev CLA 2012-01-24 07:08:44 EST
An error parser is more complex object than a property-value pair so you cannot export it like that. But it should be doable to a determined developer to add Import/Export buttons to Error Parsers preference page. In the meantime, you can "export" them by hand copying file .metadata/.plugins/org.eclipse.cdt.core/model.extensions.xml into your other workspace.
Comment 2 gregory tauveron CLA 2012-01-24 07:24:16 EST
Do you think that feature will be available in a future release?
Comment 3 Andrew Gvozdev CLA 2012-01-24 08:58:07 EST
(In reply to comment #2)
> Do you think that feature will be available in a future release?
I haven't heard it to be in somebody's plans. Unless somebody from the community is motivated enough to contribute.