From: SourceForge.net <no...@so...> - 2006-12-07 23:34:01
|
Bugs item #1458079, was opened at 2006-03-24 17:52 Message generated for change (Comment added) made by eldaaran You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=682377&aid=1458079&group_id=118870 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Support for Java 6.0 Initial Comment: I tried to a build from the latest checkout in Eclipse 3.2 M5 with Java 6.0 b76 and Jetty wasn't able to determine the VM version when I tried to launch an app. ---------------------------------------------------------------------- Comment By: Jonathan A. Leaver (eldaaran) Date: 2006-12-07 17:34 Message: Logged In: YES user_id=1352136 Originator: NO I did some research, and it looks like the virtual machine versions are hard coded into the com.iw.plugins.jetty.launcher.JettyClasspathProvider class. If you scroll to the very end, it's probably a simple fix. I bet assuming that a 1.6VM behaves the same as a 1.5VM would pretty much solve our problem. Sun has gone to extraordinary lengths to make sure Java 6.0 has the fewest possible regressions over Java 5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=682377&aid=1458079&group_id=118870 |