As far as Maven goes, this would only be the JVM used to run it - it
needs to be able to build projects using any JDK available (and the
support for that needs to first be improved).
On 7/07/2006 8:15 PM, Andrew Williams wrote:
-1 We have to support 1.4 as we a re rolling into academic environments
where the upgrade cycle is > 3 years, so many users are still new to 1.4
(though they do not know it). And to be honest I just don't trust 1.5
generating 1.4 code...
A
Brett Porter wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
