From: Andrea A. <aa...@li...> - 2003-02-09 20:03:40
|
On Sunday 09 February 2003 20:01, Andrea Aime wrote: > Ok, > it's a good step forward, but what I wanted is really a unique > javadoc with all of the classes. To show my students something > about geotools I will inevitably end up speaking about core, defaultcor= e, > shapefile, coverages, renderer and so on... it would be better > to have just one javadoc tree, just like the Java API . > And yes, I need local links, here in Italy it's still not common > to have a 24x7 internet connection, we don't pay the > provider to connect, but we pay the telephone call minute by > minute. While at home I'm almost always offline, and my students > too... > Best regards > Andrea Aime > Ah, the following bash file (apidocs.sh), placed in the geotools director= y and executed, does the trick: integrated javadoc for every module altoghether. Works only on Unix, unfortunately (but of course you can do the same with windows a batch file if you have the patience to= =20 build the sourcepath string by hand or using some other tool): #!/bin/bash cd geotools-src export SRCPATH=3D`ls -F | grep / | sed -e "s/\//\/src/" | tr '\n' ':'` javadoc -sourcepath $SRCPATH -d ../docs -source 1.4 -subpackages org.geot= ools cd .. Best regards Andrea Aime |