Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315633 - Store Texo properties in project metadata rather than in workspace
Summary: Store Texo properties in project metadata rather than in workspace
Status: RESOLVED FIXED
Alias: None
Product: EMFT
Classification: Modeling
Component: Texo (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Martin Taal CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-03 13:29 EDT by Filip Hrbek CLA
Modified: 2011-09-24 02:48 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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