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

Bug 315633

Summary: Store Texo properties in project metadata rather than in workspace
Product: [Modeling] EMFT Reporter: Filip Hrbek <filip.hrbek>
Component: TexoAssignee: Martin Taal <mtaal>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Filip Hrbek CLA 2010-06-03 13:29:05 EDT 
A project of Texo nature provides specific property settings (where to generate source, where to search for overridden templates).

Currently these properties are stored in the workspace. It would make sense to store them in the project instead so that it could be easily shared in SCM.
Comment 1 Martin Taal CLA 2011-04-23 18:47:34 EDT 
An older issue/topic. But maybe you can help me, I am not that familiar with how to solve this (is there a standard way to store something like project properties in the project?). If you have any pointers or ideas that would be great, thanks!

gr. Martin
Comment 2 Martin Taal CLA 2011-09-24 02:48:25 EDT 
Solution committed to cvs will be in next build