Currently the MITK build produces a lot of warnings. They are mostly non-critical, but this behaviour makes it difficult to spot new ones, either during developemt or on the dashboard. I suggest we go through the actual warning types that show up and decide weather
- fix it everywhere and turn on warning as error for that specific warning
- suppress it completely if it's too much effort to fix it now and file another task for it
- suppress it completely as irrelevant and document this in the code
Benefit would be a warning-free situation which hopefully prevents future errors and bugs.