This file has the same utility of templateFile.xml. The only difference is that it was projected just to control JAR files.
Which JAR files must be added in the project for which technologies.

 
In this screen we have an interesting vision of the resources of configuration of the SPIDER.
The pathTemplateFile accepted variables. $

it means that this file is in the folder common of templates (something as a library).
Moreover accepted it other types of variables.
Specifically in this example, key TECH.JAR specifies which jars always goes to be added to the project (independent of technology).
More below we have one another example: TECH.MVC.STRUTS.JAR. This key specifies which jars goes to be added to the project if the person to choose the Struts technology.

The image above is the vision in form of grid of the file templateFiles-jar.xml.
In it is possible to see clearly that some groupings of configurations exist (TECH.JAR, TECH.MVC.STRUTS.JAR, TECH.IOC.SPRING.JAR).
Inside of each grouping is specified jars necessary for that technology.