Consider compile-time plug-in handling of resources instead of hardcoding

In "legacy" there is a concept of a resource being associated univocally to a resource type.

This make a lot of sense for standardised files like .bpmn2 and .dmn and .drl, because there is a very high expectation the content of the files to be respectively BPMN, DMN and Drools Rule Language formats.

However the same is not necessarily that strongly motivated for other types of resources such as .XLS .CSV .XLSX and others

With the result that in "legacy" if a xls file is dropped in a kjar, it MUST be a drl-based decision table, or the project would fail.

Please consider for these "other types" of resource to provide a compile time plug-in mechanism, in such way we "FREE" the use of other type of asset for multiple other purposes as required, for instance:

• use of XLS to contain purely DATA to be used in a user application
• use of XLSX to be converted in other types of decision table not in DRL format