Changes for page Custom Project Templates
Last modified by Bastian Triller on 2009/04/11 21:03
From version 39.1
edited by David Holt
on 2009/03/31 19:03
on 2009/03/31 19:03
Change comment:
There is no comment for this version
To version 42.1
edited by Pascal Robert
on 2007/12/17 13:40
on 2007/12/17 13:40
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dholt1 +XWiki.probert - Content
-
... ... @@ -24,8 +24,6 @@ 24 24 25 25 If you want to look at the current templates that ships with WOLips, the best way to analyse them is by [[importing the source>>Building WOLips]] of WOLips from Subversion. The templates are located in //woproject/wolips/core/plugins/org.objectstyle.wolips.templateengine/ProjectTemplates//. 26 26 27 -If you copy a stock template to test it out, renaming the folder is not sufficient for WOLips to show the new Template in the "WO Project From Template" list. You must make sure that the template name is also changed in the template.xml file. 28 - 29 29 Without any additional metadata, the template system derives the name of the template from the name of the folder in one of the above locations. For instance, if you create a folder named ",,/Library/Application Support/WOLips/Project Templates/Wonder Application," the template system will offer a template named "Wonder Application" in the template selection dialog. Project templates found later in the list of locations above will override those of the same name from earlier in the list. For instance, a "Wonder Application" template found in /Library will overrode a "Wonder Application" template from /Library.,, 30 30 31 31 After creating a template folder, you can create a hierarchy of files and folders within that folder. When you create a project using this template, a copy of all of the files and folders in your template will be used to create the new project. It is up to you to declare //all// of the files within a project, including Eclipse project metadata files like .classpath. You can refer to the built-in project templates as a starting point for creating your own custom templates.