Mathieu! > Reasons: > - since we use OSGi as our deployment platform, I first need to > repackage everything as OSGi bundles (common enterprise libraries are > provided by SpringSource, bur not geotools, geoapi, jts, etc.) => this > is quite a bit of work and I don't want to do it on a moving target
Can you help us! I so want to include the OSGi manifest information in the geotools jars - and have a proposal here. I just lack volunteers (even myself cannot volunteer because I don't honestly know what is needed). Even if you could just review the information here and help update the steps we need to perform: - http://docs.codehaus.org/display/GEOTOOLS/Add+bundle+information+to+jar+manifest > - I expect that there would be more information about the stable > version in mailing-lists, on Google, and indeed in the documentation > > This is just to share my opinion, but even if I sometimes got puzzled > by discrepancies between examples and the library (some wiki examples > seems to be out of date, but that's common with wikis), I find the > examples very useful and then I simply dig into the code to get more > details. Yeah wiki's are a pain for being out of date; but it also represents one way in which we can collect information about what needs documentation. I think the time for wiki's have passed; our own wiki has such annoying security steps to follow due to vandalism it kinds of has lost its appeal as a community scratch pad. On nice thing about the sphinx documentation used for the webpage is that we "include" the source examples live from working code in the demo/example directory! Just so we don't run into this sort of problem.... Jody ------------------------------------------------------------------------------ _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
