dcm4che update: managed to build dcm4che-imageio

[Adi Kriegisch <adi@cg.tuwien.ac.at>]

Dear list,

I am working with Paul on getting dcm4che Debian packages and I made some
progress in this regard:

when modifying the pom-file like this:
--- dcm4che-2.0.26/dcm4che-imageio/pom.xml 2012-03-26 17:05:45.000000000 +0200
+++ dcm4che-2.0.26/dcm4che-imageio/pom.xml 2012-03-29 17:18:17.000000000 +0200
@@ -39,10 +39,11 @@
             <scope>test</scope>
         </dependency>
         <dependency>
-            <groupId>com.sun.media</groupId>
+            <groupId>com.sun.media.imageio.stream</groupId>
             <artifactId>jai_imageio</artifactId>
             <version>1.1</version>
-            <scope>provided</scope>
+            <scope>system</scope>
+            <systemPath>/usr/share/java/jai_imageio.jar</systemPath>
         </dependency>
         <dependency>
             <groupId>junit</groupId>

I am able to compile dcm4che-imageio (although some tests need to be
disabled because they fail; ie. one write test and all read tests).

As it seems something changes for maven when being called by maven helper.
I think the behaviour of maven should be consistent -- no matter if it is
called from maven helper or directly.

A patch like the above doesn't qualify for an official debian package.
Probably someone with real Java packaging skills could step up and give
some hints? :-)

Ah, and the package still isn't cleanly compiling: now dcm2txt and dcm2xml
are failing...

Any help highly apprechiated!

-- Adi