Ok, to sum up what happened here:
- we can't do it in Maven until we have better external tools support
(so, maybe for 2.1, but any significant work in JDK 5 should probably be
held until 2.2)
- Continuum forks all builds, so it should be fine, but I think it is
worth waiting until profiles are in.
- the repository manager doesn't appear to have anything holding it up.
I'm going to suggest we wait for the survey to be done before changing
anything. Since we're on the way for the next releases already, they can
stick to 1.4. It would be nice to roll the newer features in to MRM,
then Continuum, then Maven once we have a better idea of what the impact
will be.
Cheers,
Brett
On 7/07/2006 11:36 AM, 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
--
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]
