Extend main template identification

[Diusrex]

Like the README states, a main template is one which is expected to be compiled into a Java class which will be used. Therefore, a non-main template is one which is just used in other templates.

In the Umple project, all main templates were identified by .jumpjet, while all the regular templates were .jet. So the converter assumes that a file with the extension .jumpjet is a main template, while every other valid jet template is a regular template. However, other projects would likely use other ways to identify main templates.

Rather than force other project authors to adjust their templates, they should be allowed to pass different arguments to identify which templates may be main templates.

Some possible additions would include:

• All templates
• No templates (unlikely, but possible if there are multiple directories)
• Templates that start with a given prefix
• Templates that have a given suffix (not in their extension)
• Templates that contain the given substring
• Templates with a given extension (generalization of the current system)
• Templates with a given package in their directive

As a further, probably unnecessary extension, it may be possible to use some heuristics to determine if a template is a main or standard template. Some ways to guess that a template is a regular template would be if there are multiple with the same package and class name (in their directive), templates with "Ignore" in their package or class name, etc.