Hi all, As I mentioned in some previous emails, our goal for the imageio-ext project is mitigate as much as possible the risk of introducing a dependency which relies on a native library, even though such native library is well known as GDAL is. Having this objective in mind as well as the fact that imageio-ext is an open source project as well whose code is available on a public svn we have been , we are and we have always been open to suggestions/advice/RFEs, in a word collaboration. Therefore, in light of collaboration, if you have specific issues to report, like the one that you correctly reported (and that we already fixed) we are happy to take care of them, if, of course, you can share them with us. Moreover, if you have specific doubts/suggestions/criticism on the library, it would be great if you could detail them them a bit on the imageio-ml as I suggested already in the past, because otherwise it would be just us wasting our time trying to guess/understand what the reported problem could be.
Ciao, Simone. On Thu, Aug 7, 2008 at 6:39 PM, Jody Garnett <[EMAIL PROTECTED]> wrote: > Adrian Custer wrote: >> >> I've already lost time on this, on top of a bunch of other things so I >> don't have time to chase down the problems and fix them. > > You lost me? The problems seem to be in the imageio-ext project right - I am > mostly focused on the geotools unsupported plugin here. >>> >>> I was under the impression that we were getting formal when code moved to >>> a supported module; and we were going to try and not make >>> the unsupported modules available for download (or at least in a separate >>> jar). >> >> yes, that seems reasonable and was my understanding as well. >> > > Suppose I better go visit the 2.5.x branch and make sure that happens. >> >> I haven't looked at the code of the Geotools module itself; I'm assuming >> that's clean since our review for graduation was exhaustive. That's not the >> code that's at issue. > > Okay so what we have then is how we handle our dependencies; something the > developers guide (and thus the community) has not through through in great > detail. >> >> The code that's at issue is the external stuff pulled in by this module >> when it builds. Building the module pulls in the code from the >> imageio-ext project off in sun's sourceforge equivalent whatever it's >> called. > > It is called java.net. >> >> A quick look at that code raised a bunch of issues which is both good and >> bad: good that that is documented bad that we can't distribute >> the code. >> > > I see; I am signed up to the imageio-ext email list; perhaps that is a > better venue to talk about this? From our standpoint at geotools we do get > email threads on the user list when a large organization has "performed a > code audit" and found some issues to deal with. I would expect us to handle > the situation in a similar fashion. >> >> My review was trivial. I opened all the license.txt files then opened all >> the java files. Just reading the documented stuff showed me that the code >> needs work, thinking, fixing, before it can even be read. >> > > I think we are mostly worried about license / distribution end of things > here correct? >> >> Distribution places additional restrictions which Geotools cannot meet >> today. So there's work there but the project is being worked on so it should >> get to the point where it can work. >> > > Okay let us pass these concerns over to the imageio-ext project. If uDig and > GeoServer wish to include the work (or if any project wants to include an > unsupported module) that is kind of up to them. For GeoTools I want us to > treat unsupported modules very carefully. > > Cheers, > Jody > -- ------------------------------------------------------- Eng. Simone Giannecchini President /CEO GeoSolutions S.A.S. Via Carignoni 51 55041 Camaiore (LU) Italy phone: +39 0584983027 fax: +39 0584983027 mob: +39 333 8128928 http://www.geo-solutions.it ------------------------------------------------------- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
