> Manuel, as you worked with the code, could you estimate how much work it would be to fix > CLEREZZA-265 without the LGPLed library?
I had a closer look at im4java, which I used to fix the problem. They also use the command line tool for executing imagemagick functions. The basic difference seems to be that they are creating temporary files and provide them as parameters instead of using input and output streams directly as we do. If that is the cause of our trouble, I think it could be fixed within a day. We already have a variant of this imagemagick project in our repository with my fix in it (using im4java). Removing this project from apache clerezza seems to me an option also. Cheers, Manuel On Mon, Oct 18, 2010 at 10:57 PM, Reto Bachmann-Gmuer <[email protected]>wrote: > Hello > > For a long time CLEREZZA-265 has been open know, essentially the issues > asks for support for newer versions of Imagemagick. The tests are only > executed when the right Version of Imagemagick is available and apparently > hang (according to CLEREZZA-326). > > Manuel has been working on CLEREZZA-265, unfortunately the chosen approach > had to be reverted for license reasons (lgpl library). > > What shall we do? I see the following options: > > - Ditch the imagemagick bundle. As CLEREZZA-265 got votes and > Imagemagick creates better quality images than the java2d libraries this is > probably not a very popular option. > - Implement support for more versions of Imagemagick without using LGPL > code, and fix the problem with hanging test. Due to the many Versions of > Imagemagick, I think this would be a big task. > - Donate Manuel's LGPL code to a project outside Apache that provides > Clerezza Bundles that cannot be part of an Apache project (in a future > Clerezza components and update manager such a project could then be in the > "multiverse" index... ). > > Other ideas? > > Manuel, as you worked with the code, could you estimate how much work it > would be to fix CLEREZZA-265 without the LGPLed library? > > Cheers, > reto >
