Automatically install plugins necessary for template-sets

[MikeSchumacherCapgemini]

As a cobigen user, I want cobigen to automatically install the plugins necessary for generation so that i do not have issues related to necessary plugins when it comes to generation.

Acceptance Criteria

• plug-ins necessary for a template-set should be specified as maven dependency within the template-set
• plug-ins conflicting (in case of already installed plug-in in eclipse vs. the same in a different version specified in a template-set) should be resolved by preferring the template-set configured plug-in with a WARN notice on the log
• plug-ins specified in one template-set should be just loaded for templates within the template-set.
• in case multiple template-sets are involved in a generation, cobigen needs to make sure, that plug-ins specified by template-set A are not taken into account for generation of templates of template-set B

[Ali7223]

As of now CobigenUtils class loads all the dependencies declared in cli-config pom and Lookupservices is called after the retrieval of dependencies as URLClassLoader specified in a cli config pom.xml and we would like that at this point the template-set project pom is considered and relative dependencies required for generation are loaded.
Lookupservices iterates through all the URLS in class loader and as of now it loads all the plugins in generatorPluginActivatorClasses since we have declared all the plugins as dependendcies in cli-config pom.xml.
Further getTriggerInterpreter method in PluginRegistry class selects which plugins to activate after reading the file extension name.
Triggers are activated by file extensions but what files should be generated is selected by means of selected increments. The plugins for relative file extensions specified
in increments are to be added in pom.xml of the given template-set project. Now the question arises at what point the specific templates project should be considered(for loading its dependencies)?
The Idea to achieve the acceptance points of this ticket is that we first check what increments have been selected and register plugins specified in their respected projects pom.xml and load their URLs in ClassLoader since there are methods already available for doing such task in CobigenUtil class registerPlugin method is one of them.
In case of a conflict we could use resolvedependencies method present in MavenUtil Class to choose which plugins to prefer for a specific template-set.
There might be a problem with this approach since most of the loading process will be done after selecting the increments which might make the process slow.
I would also appreciate your feedback

[maybeec]

seems that there is some work being done on this on branch 1494-wip-template-set-plugin-loader-felix. Could someone check the state? Can we create a PR ?

[NelsonNew]

Possible solution is to incrementally generate and use for each generate only one template with template-set-specific dependencies.