The introduction of the new dashboard script revealed that the PluginGenerator tests fail. I already fixed a PATH issue with the Windows mitkPluginGeneratorCreateTest but the remaining errors are actual test errors.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | kislinsk | T27701 Overhaul or remove PluginGenerator | ||
| Open | kannberg | T28585 The MITK-Tutorial Step 9 missing inheritence |
Event Timeline
Comment Actions
Since we have this task now I suggest to deactivate them "somewhere globally" and discuss later how to proceed. My guess would be it is quite some effort. Having tests for the generator, packging and the extension mechanism is very important I think, but I'm not sure what the current tests cover and if it's worth to fix.
Comment Actions
Yes, let's deactivate them for now (again), and discuss it in the next MITK meeting.
Info for the meeting/ideas we already had:
- Getting rid of the project generation part as we want to focus on the MITK-ProjectTemplate and fix the plugin generarion part
- Getting completely rid also of the actual plugin generation part (like, use a plugin template of MITK-ProjectTemplate)
- Fix everything (do we really want to maintain a 3rd "build system" in parallel?)
Comment Actions
We discussed this task in the MITK meeting and we want to go with option (1). In addition, we want to syncronize the branches of rMITK MITK and rMPT MITK-ProjectTemplate and add the project template as extension to all of our CI clients. We should also look into the new template repository feature of GitHub.
Comment Actions
@kislinsk : I just noticed we had some earlier discussions and there is a branch which fixes two minor issues, not sure if relevant for option (1):
Comment Actions
Would be nice if a note is added to the documentation that the MitkPluginGenerator is currently not active. :)