Justin Deoliveira a écrit : > I see. Hmmm, to be honest all the "custom" stuff in our build, and even > more in the site generation is *very* error prone ( or least it has been > for me ). For instance, I don't think i have every been able to > successfully generate javadocs. Perhaps once but i had to use java 5 to > do it. Its not a wonder why geotools is released so seldom.
Created a JIRA task: http://jira.codehaus.org/browse/GEOT-1253 As far as Javadoc is concerned, it does require Java 5. It uses standard javadoc tags introduced in Java 5. We also have a custom taglet (gt2-javadoc) which was wrote at user's request: users wanted to know in which modules are defined each classes. The taglet API was not stabilized in Sun's JDK before Java 5. Things may become easier when Geotools will be allowed to target Java 5: Javadoc will work with the same JDK, the "unsupported/geometry" module will become an ordinary module (no more "enable on Java 5" profile hack) and we will not need anymore the "geoapi-nogenerics" hack. I really miss generic types, and my code has many "todo: uncomment when we will be allowed to compile for J2SE 1.5". Carrying Java 1.4 compatibility is becoming heavier and heavier... Martin ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
