It seems to me that the consensus is to stay with 1.4 (or not, in any case...) on a related note: Does it make sense to have plugins require a specific version of jdk to run? This would allow the plugin toolkit to make use of current language constructs (annotations), but reducing of portability. Effectively, giving the plugin author the choice, whatever his or her requirements are.
Am I off base here? I don't see where this currently exists, and I saw no mention of this in the 2.1 design doc. Thanks; Eric ---------- Forwarded message ---------- From: Brett Porter <[EMAIL PROTECTED]> Date: Jul 6, 2006 8:36 PM Subject: [discuss] Java 5 To: Maven Developers List <[email protected]> Hi, I wanted to get thoughts on starting to require a Java 5 JVM to run stuff we build. We currently restrict to 1.4 across the board. Here's what I'm thinking: - MRM and Continuum should switch now. Stuff built there is rarely consumed elsewhere, and a Java 5 requirement outside of that is reasonable - We could switch for Maven 2.1, as long as we have improved support for invoking external toolchains. This would facilitate doing some much nicer stuff with plugins like annotations. - A generified plexus would be very cool, but is an aside here and post plexus-1.0 in my opinion. - I think it's best to keep the lower requirement on Doxia, Surefire (1.3), and Wagon for now. Does anyone have any thoughts on this? I'll likely propose a vote on the first point before the first/next releases of them unless there are reasons not to. Cheers, Brett -- Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
