Changes for page Custom Project Templates

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -131,17 +131,10 @@
131	131
132	132	In addition to variables inside of Velocity templates, you can also use template variables in folder and file names. However, because $ is not allowed on some filesystems, we instead surround the variable names with "" (for instance $someVariable would be "someVariable" in the filename or path). As an example, the template above has an input named "basePackage" (of type Package) which, as we learned above, creates two variables: "basePackage" and "basePackage//folder". Since we are going to be using this variable to name (and define the path) of a folder in the Sources directory, we need to use the alternate version of the variable. Create a new folder in the Sources directory of the project templaet and instead of using "${{basePackage_folder}}{{/basePackage_folder}}" as the file name, we must use "basePackage//folder".
133	133
134		-= Special Circumstances =
	134	+=== Special Circumstances ===
135	135
136	136	===== Flagging files to be skipped by Velocity =====
137	137
138		-If there are files in your template that should not be processed by Velocity as the project is being setup, you will need to end the file name with "binary" which will cause Velocity to strip the "binary" off the file name, but skip processing the contents of the file. Examples of files that you'd want to flag are:
139		-
140		-* EOGenerator Templates
141		-* Custom builder .launch files.
142		-
143	143	===== Using keypaths =====
144	144
145		-* If you need to call a method on a given variable, you need to include the "()" at the end of the method name. An eample is in the build.properties file. In order to get the lowercase version of the project name, you have to call "${{projectName.toLowerCase()}}{{/projectName.toLowerCase()}}"
146		-
147	147	Happy templating