Andrea Aime wrote: >> So "spike" or "unsupported" look to be the best bet? You were not >> planning on writing user documenting these up and meeting our QA >> requirements in two days are you? > Jody, as I noticed in my first mail, the arcgrid _stable_ plugin > depends on both customstreams and asciigrid. So these need to be > versioned along with Geotools, and cannot be put in spike. > Having them in unsupported would somehow work, it would just be > strange to have a supported plugin depend on unsupported modules. Agreed Andrea - our organization system has broken down in this case...
extension? No. I would find a plug-in depending on an extension even more strange (it would completely wreck the layers diagram for GeoTools). unsupported? No. We need to be able to ship geotools without any of the modules in "unsupported",. plugin? Yes. I think the best advice is to ship these as a "plugin" and if the plugin is for ImageIO (and not directly for the GeoTools library) then that is just water under the bridge. Recap Question: Can we do anything other then "unsupported"? I am not sure if Simone has plans to meet QA test coverage and user doc needs over the next two days... Cheers, Jody ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
