This would have zero impact on applications built with Maven.
I'd been meaning to follow this up. Let me see what happened with the
user survey...
- Brett
On 26/11/2006, at 12:49 PM, Brian E. Fox wrote:
Our experience with our products is that not enough of the available
portal and app servers support JDK 1.5 or our customers haven't yet
upgraded. That unfortunately means we are stuck on 1.4 for the near
future. I think many business customers are in the same predicament
where we can't dictate the JDK required. If maven suddenly required
Java
1.5, we would be in a serious bind and it would limit adoption of
Maven
2.1.
-----Original Message-----
From: Rahul Thakur [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 25, 2006 7:55 PM
To: Maven Developers List
Subject: Re: [discuss] Java 5
This thread kinda died off silently....
Just wondering if there was a user survey about switching to Java 5.0?
Rahul
----- Original Message -----
From: "Jason van Zyl" <[EMAIL PROTECTED]>
To: "Maven Developers List" <dev@maven.apache.org>
Sent: Sunday, July 09, 2006 6:09 AM
Subject: Re: [discuss] Java 5
On 7 Jul 06, at 2:36 AM 7 Jul 06, 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.
I think before this can be done we need to make sure we're not making
life difficult for people. It may be the case that most people don't
have a problem using a 1.5 JDK in their environment but it might be
an ideal time to use one of the online survey services to take a real
poll. If the vast majority of users were not adversely affected by a
move to 1.5 I would be fine with, as I'd like to use 1.5 where
possible. But if it's not the case we probably should hold off on
this requirement.
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]
Jason van Zyl
[EMAIL PROTECTED]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
