Clean up, improve and test PluginGenerator, ProjectTemplate and MITK_EXTENSION_DIRS mechanism
Closed, DuplicatePublic
Actions

Assigned To

Authored By

	nolden
	Feb 10 2020, 11:40 AM

Description

Several issues have arised around our various extension helpers and mechanisms:

currently the PluginGenerator tests are not executed on the dashboard. Manual execution fails, e.g. http://cdash.mitk.org/testDetails.php?test=13645913&build=717610
there is both a project template repository ( https://github.com/MITK/MITK-ProjectTemplate ) as well as a subdirectory in the MITK source tree ( https://github.com/MITK/MITK/tree/master/Applications/PluginGenerator/ProjectTemplate ) . Maybe we can make more clear what the difference is or remove one of them. Also some test should be established that validates it works
Related is https://github.com/MITK/MITK/tree/master/Applications/PluginGenerator/PluginTemplate and the documentation on http://docs.mitk.org/nightly/NewPluginPage.html

nolden triaged this task as Normal priority.Feb 10 2020, 11:40 AM

nolden created this task.

nolden added a subscriber: kislinsk.

I would like to see the plugin generator loosing complexity by removing its project template capabilities
The current approach is https://github.com/MITK/MITK-ProjectTemplate
The project template is based on the last release, resp. releases/2018-04
The project template is an MITK extension
MITK extensions can be easily set in a recent version of our CDash script
To test the project template, we need separate build clients based on the last release instead of master, no specific test has to be executed (see bullet point above)
A few tests are currently not executed because I removed CTest subproject labels for testing purposes and I forgot to reintroduce them
Instead of simply adding them again, I vote for a better label than "MITK" or "MITK-Plugins" like "MITK-Packaging"