Justin I know you are away on holiday; the OGC familly of modules is holding up the OSGeo release train; we have two things here: - the code is auto generated; so the best way to fix the headers is to modify the generation program (in build somewhere?) - the schemas contained here are (c) OGC are they not? But I suspect we needed to do a bit of hacking to make them work...
Without Justin's clarification can we assume the following two issues need to be created: - modify the code generator with new headers - hunt down the license on the OGC schemas and include it in the module ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
