dcm4che migration

[Enet4]

Dicoogle currently still uses dcm4che-2.x, which is deprecated. More than once plugin developers have opted in to embedding more recent versions of dcm4che for other tasks at the price of not being fully compatible with other core constructs. Sometimes they even wanted to use newer versions, but had trouble integrating them with Dicoogle, so they ended up making workarounds.

Let this issue be used to track future updates to dcm4che and decide when and how to push these changes. We also need to make an assessment of how much of dcm4che is used, both in sdk and core. The core Dicoogle project may be able to contain multiple versions, but the API in the SDK is a critical integration point.

After some discussion, we have decided to migrate the core project and the SDK to use the latest dcm4che (v5) in Dicoogle 4. It is simple an effective, only requiring one large migration step.

[Enet4]

In my opinion, we should take the quick and painful approach of migrating everything to use the latest dcm4che at once, because the cost of migrating all core and plugins at once would pay off early and be less expensive than diluting that effort to subsequent versions.

[bastiao]

In my opinion, we should take the quick and painful approach of migrating everything to use the latest dcm4che at once, because the cost of migrating all core and plugins at once would pay off early and be less expensive than diluting that effort to subsequent versions.

Yes, we have been defining and implementing a strong methodology for validation, this will give some safer guarantees to do it.