As per Steve's suggestion, template provider is more useful and male more sense.

Current sample application provider allows contributor makes sample application contribution in form of eclipse plugin by extending extension point defined in sample app provider. sample app provider provider mechanism to retrieve, validate, list sample applications. This is designed not to allow further modification.

Template provider, on the other hand, is designed for further customization.
Changes includes:
- dependent libraries defined in template will not be changed
- other libraries is allowed to turned on/off
- make web.xml and faces-config.xml optional as in most cases template doesn't have special web.xml other than default one. faces-config.xml may not be required. Making web-xml-path and faces-config-path optional so that for template, there is no need for a special xml files and for sample application, these 2 pathes may need to be specified.

Both provider and integration core need to be changed.