Justin Deoliveira wrote:
I am all for Java 5 interfaces. They are much more expressive and can
potentially save a lot of time. That being said the trouble is that it
takes time to switch between Java1.4 and Java1.5 interfaces, its not
an automatable process.. The GeoAPI script semi-automates the process,
but you still have to modify the ant script when an change is made to
an interface.
Retroweaver automates the process, but doesn't do source level
transformations. So users have to develop against Java 1.5 all the
time, and then just deploy in Java 1.4.
I am not sure the Java1.5/1.4 split will work until the community
decides as a whole that Java1.5 is worth it.
Still the GeoAPI approach would give us 80% of the benfit. Note - we did
meet the letter of the Developers Guide law w/ respect to waiting for
Java 5 already (Java bumped its version numbers around since this was
written).
-<http://docs.codehaus.org/display/GEOTOOLS/Language>
But I understand that waiting for J2EE to move is more politic.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
