Brett, I am using M1 to build for Websphere 4, which runs on JDK 1.3. Asking the 50+ developers in my project to install another JDK, which is not supported by the AS, doesn't seem reasonable to me, certainly if it's for a minor upgrade. In my opinion, you shouldn't introduce this type of major modifications in a minor release. Leave that for M2... I know there are many other projects out there that are still using 1.3. Adding another JDK is often not that staightforward. You have to have a very good reason to do so.
Thomas. On 5/1/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > Hi, > > I wanted to make sure users are aware of this - some of the new code > being introduced to Maven 1.1 and 2.0 requires a 1.4 JVM to run. This > does not mean that it can not build for anything else - you can still > target 1.1, and can even compile using a completely external JDK IIRC. > This is just a matter of what JVM runs Maven itself. > > This still seems to be a problem for some. If anyone is in this > position, can you please shed some light on what the requirement is? > That is if you -can not- install a 1.4 JDK to run Maven with. I'm > thinking this can only be because one is not available for a > particular operation system, of which I am not aware of any at this > point. > > I don't see the position on this changing as it requires a fair bit of > code change for little benefit, but I would like to know the impact. > > Thanks, > Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
