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 ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
