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.
-Justin
Matthias Basler wrote:
Hi Jody,
on the last IRC you mentioned that there's no place in GeoTools for alternative
Java5 interfaces (for better usability).
I just thought this a good idea. So, why not create a place to collect them?
One could then create "altenative" jars that include the Java5 interfaces
instead of the Java1.4 interfaces. Just as it is done in GeoAPI.
I am sure the GeoTools users would like this.
Would this work?
Matthias Basler
[EMAIL PROTECTED]
----------------------------------------------------------------
This mail was sent through http://webmail.uni-jena.de
-------------------------------------------------------
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
-------------------------------------------------------
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
