I will go ahead with extension, but this actually hits on something I have wanted to bring up lately, in that I think we are outgrowing our current organization scheme. I will start a separate thread for this but I think "extension" becoming the place where we are starting to put everything is a symptom of needing a new organization scheme.
-Justin Jody Garnett wrote: > Understood; when the parser is deemed ready I thought it would move to > library as well? > > How about we place it in extensions (so we can get on with life) and > consider moving when the parser is ready... > > Jody > > On Tue, Jun 9, 2009 at 5:35 PM, Andrea Aime<[email protected]> wrote: >> Jody Garnett ha scritto: >>> I extensions or library? Extensions is getting a little heavy and non >>> optional these days. >> If we had to move them to library, what would be of the parser? >> xsd-core in library, all the others in extensions? >> >> I was suggesting extensions because of the tight bound between the >> models and the xsd parser. >> >> Cheers >> Andrea >> >> -- >> Andrea Aime >> OpenGeo - http://opengeo.org >> Expert service straight from the developers. >> -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
