Hi Jeremy, I remember that we started this discussion a little while back. I'm not aware of any consumers who depend on Java 1.4 but that doesn't mean they're not out there. We will need to probe the community (through posts like yours) to see if this change will affect anyone.
In general, I don't think we should make this switch unless there is a tangible benefit. At this point I think we need to keep pushing for a v1.0 of Woden that provides a WSDL 2.0 validating parser. We still have a lot of work to do with the assertions, the OM model, and our tools. I don't think moving to Java 5 is a priority. However, if we don't hear any negative feedback for this change perhaps we can start using the Java 5 features without reworking the entire API at this point. Lawrence From: "Jeremy Hughes" <[EMAIL PROTECTED]> To: [email protected] Date: 07/14/2008 04:50 AM Subject: Move to Java 5? Hi all, Axis2 (and related projects) have all moved (or are moving) to depending on Java 5 in their trunk. Is this feasible for us? It would give us opportunity to modernize the API with generics. CXF also depends on us. I just checked their pom.xml [1] and that depends on java 5. Are there any other consumers of Woden that require Java 1.4 still? [1] https://svn.apache.org/repos/asf/cxf/trunk/pom.xml Thanks, Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
