About the paragraph I added at the end of this page:
http://docs.codehaus.org/display/GEOTOOLS/Supporting+Hacks+and+Versions
Jody Garnett a écrit :
Um I ment an usage example, that article is trying to show to geotools
programmers what the options look like to them.
I tried to add some more details, but I can hardly do much more.
Developers really need to learn annotations if they want to understand
this proposal. It seems to me that trying to explain more is like trying
to explain what annotations are, which is out of my scope.
Except for the inconvenient cited below, I strongly suggest to use
annotations because it keep all doors open: javadoc, interfaces or
(maybe) compile-time warnings (the later need investigation in order to
determine if it is really possible). We can do everything cited in the
"Supporting Hacks and Versions" page automatically with annotations, at
our choice.
The inconvenient is that annotations require J2SE 1.5. We can probably
hack the build in order to generate J2SE 1.4 compatible code. But given
the trouble that it would involve, this bring back again the question:
when will we be allowed to target J2SE 1.5? Note that the public review
ballot for J2EE 5.0 (the last step before J2EE adoption as an official
specification) closed on August 2, 2005. I don't know yet when Sun
implementation will be available.
Martin.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
