JettyLauncher

Please, anyone ... upload that jar file to the update site. I'm not able
to build the plugin locally :(

Logged In: NO

I have Eclipse 3.3 in order to fix this. I changed getVMType in
JettyClasspathProvider

import org.eclipse.jdt.launching.IVMInstall2;

private int getVMType(ILaunchConfiguration config)
{
String versionString = null;

IVMInstall install = JavaRuntime.getDefaultVMInstall();
if (install instanceof IVMInstall2) {
IVMInstall2 install2 = (IVMInstall2)install;
versionString = install2.getJavaVersion();
if (versionString.indexOf("1.1") > 0)
{
return VM_11;
}
else if (versionString.indexOf("1.2") >= 0 ||
versionString.indexOf("1.3") >= 0)
{
return VM_12_13;
}
else if (versionString.indexOf("1.4") >= 0 ||
versionString.indexOf("1.5") >= 0
|| versionString.indexOf("1.6") >= 0 ||
versionString.equals("???"))
{
return VM_14_15_16;
}
}
return VM_ERROR;
}

I dropped you a line through the sourceforge contact page. I hope it
reaches you. Subject was "jettylauncher".

Cool. We are still looking for people to take over the project. There
seems to be enough interest in it, but the committers (all three) just
can't get to support this anymore. Please drop me a line when you are
interested.

Here http://jax.be/jettylauncher.jar is an updated jar file where the
versionString.equals("???") has been changed to
versionString.indexOf("1.6") >= 0. It doubled in size after I updated it
when the newly compiled JettyClasspathProvider.class but it works!

Put it in eclipse/plugins/com.iw.plugins.jettylauncher_1.4.1.

Any news on when/if this patch is going to make it?

Yes, in fact, changing line 397 from:

|| versionString.equals("???"))

to:

|| versionString.indexOf("1.6") >= 0 || versionString.equals("???"))

and recompiling the plugin definitely fixes this problem.

Here's what I've got:

### Eclipse Workspace Patch 1.0
#P com.iw.plugins.jettylauncher
Index: src/com/iw/plugins/jetty/launcher/JettyClasspathProvider.java
===================================================================
RCS file:
/cvsroot/jettylauncher/com.iw.plugins.jettylauncher/src/com/iw/plugins/jetty/launcher/JettyClasspathProvider.java,v
retrieving revision 1.19
diff -u -r1.19 JettyClasspathProvider.java
--- src/com/iw/plugins/jetty/launcher/JettyClasspathProvider.java 11 Oct
2004 10:41:46 -0000 1.19
+++ src/com/iw/plugins/jetty/launcher/JettyClasspathProvider.java 8 Dec
2006 00:23:59 -0000
@@ -394,7 +394,7 @@
return VM_12_13;
}
else if (versionString.indexOf("1.4") >= 0 ||
versionString.indexOf("1.5") >= 0
- || versionString.equals("???"))
+ || versionString.indexOf("1.6") >= 0 ||
versionString.equals("???"))
{
return VM_14_15;
}

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.