search

xinster819 / run-jetty-run

Automatically exported from code.google.com/p/run-jetty-run
0 stars 0 forks source link

Java compiler version issues with JSP and Jetty #32

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install the latest run-jetty-run plugin from the updatesite
2. Start the plugin
3. Try to access a jsp

What is the expected output? What do you see instead?
Expected output is the rendered jsp. What I see is a blank page with the
following error
java.lang.NoSuchMethodError:
org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/j
dt/core/compiler/IProblem;

What version of the product are you using? On what operating system?
run-jetty-run 1.1.1

$ java -version
java version "1.6.0_06"
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) Server VM (build 10.0-b22, mixed mode)

on linux fedora 11
$ uname -r
2.6.29.4-167.fc11.i686.PAE 

eclipse 3.4.2 Build id: M20090211-1700

Please provide any additional information below.

Original issue reported on code.google.com by matt.mil...@gmail.com on 26 Jun 2009 at 11:09

GoogleCodeExporter commented 9 years ago 
Matt, it's interesting that the Eclipse java compiler is mentioned.  I don't 
know why 
that would be used in this situation (of course, I'm not an expert on jsp 
compilation).

Would you be able to produce a small test case that demonstrates the problem 
(i.e. an 
eclipse project you could attach to the bug)?  Thanks.

Original comment by James.Sy...@gmail.com on 27 Jun 2009 at 12:23

GoogleCodeExporter commented 9 years ago 
Actually after a bit more investigation I'm not sure this is an issue with
RunJettyRun. What I've discovered is that the jsp libraries that jetty uses are
compiled using version 3.1.1 of the eclipse jdt core library. But I'm trying to 
run
in an eclipse version that uses version 3.2.0.xxx of the core library. The 2 
versions
are incompatible, hence the java.lang.NoSuchMethodError. I did manage to fix the
problem by using 1.0.1 of RJR and modifying the source to put the 3.1.1 jar 
first on
the classpath before the eclipse 3.2.0.xxx version. I tried the same trick on 
RJR
1.1.1 but the 3.2.0.xxx version was still appearing first on the classpath so 
the
problem still occurred. Maybe I need to understand the differences between the 
way
RJR 1.0.1 and 1.1.1 build the classpath. Anyway I think this issue can probably 
be
closed as it's not a RJR problem and I've found a workaround.

Original comment by matt.mil...@gmail.com on 3 Jul 2009 at 10:19

GoogleCodeExporter commented 9 years ago 
Matt, thanks for the update.  If you do learn more about the cause, I'd be 
interested 
in hearing about it.

I'll leave the bug open at low priority, as a reminder that I need to add jsp 
tests.

Original comment by James.Sy...@gmail.com on 3 Jul 2009 at 3:35