(user votes)
+1 Starting with Continuum/MRM as it might trigger some issues which
yield experience before doing Maven
+1 On FAQ documentation on how to run maven in JDK 1.5 but compile with
JDK 1.3/1.4 API's (not just -source).
I would really like the ability to write tiger annotated maven
plugins... but as I understand that the minimum JDK for plugins is the
same as the minimum JDK for maven itself. That's probably a good thing, so:
+1 for maven, in a few months.
For NetBeans: would it be possible to say "Netbeans works on 1.4 but the
netbeans maven plugin only works if you are using JDK 1.5"?
To compare: "Acegi works on 1.4 but the acegi-tiger module only works if
you are using JDK 1.5".
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
--
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
