Retroweaver looked pretty promising, complete and handles pretty much
all of the Java 1.5 capabilities. I was planning on doing some testing
of the 1.4 compatible code in a J2EE container, but never got around to
it. Unfortunatley Retroweaver doesn't do code level tranformations.
If the community did decide to move to 1.5 it would be a pretty seemless
way to stay backwards compatible. Something easily integratable into the
build scripts.
Justin
Jody Garnett wrote:
Martin Desruisseaux wrote:
Jody Garnett a écrit :
GeoTools2 module build report 20050923
gt2:referencing cleaned
It was caused by an accidental J2SE 1.5 dependency. Fixed as of
revision 15841.
Thanks Martin - hopefully not something I did ;-)
No, it was my fault.
I can't wait the day when we will switch to J2SE 1.5 :)
Justin was looking into retroweaver, and your ant script for geoapi. He
ended up backporting the udig catalog api by hand.
But perhaps he can share is research/impressions with us?
Jody
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
