[DISCUSS] Should we re-enable the JVMCheck warning message for the 2.0 release?

2007-04-10 Thread Donald Woods
Wanted to see what everyone's opinion was before I integrate the patch for G2759 - https://issues.apache.org/jira/browse/GERONIMO-2759 which re-enables the JVMCheck code that we had in 1.1 to warn users if they try to run the server on a non-Java SE 5 JVM (like Java SE 6.) -Donald

Re: [DISCUSS] Should we re-enable the JVMCheck warning message for the 2.0 release?

2007-04-10 Thread Matt Hogstrom
I it needed ? What would we expect not to work? On Apr 10, 2007, at 10:17 AM, Donald Woods wrote: Wanted to see what everyone's opinion was before I integrate the patch for G2759 - https://issues.apache.org/jira/browse/GERONIMO-2759 which re-enables the JVMCheck code that we had in

Re: [DISCUSS] Should we re-enable the JVMCheck warning message for the 2.0 release?

2007-04-10 Thread Aaron Mulder
I would think we'd need to check for Java 1.5 more urgently than Java 1.5. Thanks, Aaron On 4/10/07, Donald Woods [EMAIL PROTECTED] wrote: Wanted to see what everyone's opinion was before I integrate the patch for G2759 - https://issues.apache.org/jira/browse/GERONIMO-2759

Re: [DISCUSS] Should we re-enable the JVMCheck warning message for the 2.0 release?

2007-04-10 Thread Jason Dillon
Using a 1.5 JVM is more likely to barf up a class version incompatibility... unless the bootstrap modules (and their libraries) are compiled to be compatible with 1.4, but I don't think that is worth trying to enforce. I don't see any point in adding this extra warning layer muck.