Bug 452431 - Template location must be in the plug-in project
Summary: Template location must be in the plug-in project
Status: RESOLVED INVALID
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 1.0.1   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Doug Schaefer CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2014-11-20 01:15 EST by Marc Ernst CLA
Modified: 2017-07-29 15:13 EDT (History)
1 user (show)

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 Marc Ernst CLA 2014-11-20 01:15:58 EST 
Extending templates is getting complicated only because of the issue that the location of the templates.xml must be in the plug-in project. The idea was that the user can download new templates from the internet via a small tool which modifies an external plug-in xml. This plug-in xml could be read with the IExtension registry to add the contributions dynamically. The only problem with this solution is that the templates.xml must be in the plug-in project. I would be also nice to have a workaround for the moment which tells the template engine where the template xml is located in the system.
Comment 1 Nathan Ridge CLA 2017-02-07 19:59:35 EST 
I'm not sure I follow this. What is "the plug-in project"?
Comment 2 Nathan Ridge CLA 2017-07-29 15:13:34 EDT 
Closing as there has been no response to comment 1.