>
> So Justin this ends up being what you can pull off. If that is organize
> by specification so be it. Would you make these
> child modules of library/xml - or place them over in the plugins folder.
> I do not believe they contribute new API so
> they could be stored in plugins.
>
We mulled over this before. They do provide new api in that users depend
on them directly. So if I am not mistaken this makes them extensions
rather then plugins.
I would be ok with putting them under library/xml. The question then
becomes how to arrange the modules so that people dont get a wack of
eclipse depdendencies that they didnt ask for.
If the notion of extensions is well received, how about this:
module/
libary/
xml/
xdo/ ( not sure what to call this one )
xsd/
extension/
xml/
filter/
gml/
sld/
...
-Justin
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
-------------------------------------------------------------------------
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
