But you would easily be able to run an Ant build that did something like replace all ElementClass with java.lang.Object, right?
We would just have two Ant targets:
ant jar ant jdk15jar
David Morris wrote:
Gavin,
I do most of my work against the iSeries. IBM generally trails Sun by about 6-9 months on full JDK releases so that may keep us out of the game for about a while. Some of Sun's developers privately recommend waiting for the .1 release before using a new JDK in production environment. Going with 1.5 mean that some of us will not be able to help you with testing in anything but a minimal development environment. I would balance this against writing the code with the best tool for the job. Because of this I would wait for 2.2.2 (assuming 2.2.1 might fix some minor bugs).
David Morris
Gavin King <[EMAIL PROTECTED]> 02/11/04 9:44 PM >>>
I'm considering implementing support for JDK1.5 generics in the v22branch. This means that 2.2 would not be able to be compiled in older JDKs until we got a new ant build target that would do some source pre-processing.
What do you guys think?
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-- Gavin King JBoss Group +61 410534454 http://hibernate.org
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
