Nick Sieger wrote:
It's funny, suddenly I take a look around and it seems like the same
conversation is happening all over the place. Lucene [1] and CXF/XFire
[2] are two examples I came across today. [2] is worth reading to
remind yourself that retroweaver/retrotranslator are not perfect, and it
will be possible for code to drift away from weave-ability.
[1]: http://www.gossamer-threads.com/lists/lucene/java-dev/51605
http://www.nabble.com/The-JDK-1.5-Can-o'-Worms-t4138703.html
<http://www.nabble.com/The-JDK-1.5-Can-o'-Worms-t4138703.html>
[2]: http://www.nabble.com/RE%3A-Java-1.4-p11653138.html
At this point I'm not myself concerned about Java 1.4. The retroweaver
stuff I added in was to at least show it can be possible to maintain a
weaved version, and that with what little Java 5 stuff we're using now
we're still in the clear. Outside that, I'm not going to worry about it
all that much...I'm for Java 5.
I think getting unit tests up and running on the weaved JAR will help a
lot with ensuring we're not drifting too far away. And I think one
problem many projects run into is trying to do a mass conversion to Java
5 features; lo' and behold, it turns out some of them don't weave. We'll
take it slow, use things that actually serve a purpose for us, and count
on unit tests and actual 1.4 users to keep us honest. Outside that, the
benefits of Java 5 are too great to ignore any longer.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
