Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346180

Summary: JSP-2.2 support in jetty-8 is broken
Product: [RT] Jetty Reporter: Hugues Malphettes <hmalphettes>
Component: osgiAssignee: Hugues Malphettes <hmalphettes>
Status: RESOLVED FIXED QA Contact:
Severity: blocker    
Priority: P3 CC: janb, jetty-inbox
Version: 8.0.0   
Target Milestone: 7.2.x   
Hardware: All   
OS: All   
Whiteboard:

Description Hugues Malphettes CLA 2011-05-17 22:18:05 EDT
At the moment we are blocked by this bug:
http://java.net/jira/browse/JSP-21
Comment 1 Hugues Malphettes CLA 2011-05-23 22:43:26 EDT
Ok our friends at java.net/jsp have applied the patch.
We have clearance on the IP side (CQ-4711) to apply the patch to the already approved version of jsp-impl.
We are working on a build and it will be pushed to maven central most likely somewhere under the org.mortbay group-id.
After this it will be all good in jetty-8-jsp land.
Comment 2 Jan Bartel CLA 2011-05-25 02:54:08 EDT
Some updates checked into jetty-distribution to use the orbit jars for:
 * el
 * taglibs
 * jstl
 * jsp-api

For the moment, the jetty-distribution pulls the jsp-impl jar from maven org.mortbay.jetty.jsp-impl-2.2.2.b05.0.jar. When this is put into Orbit, the pom should be updated to pull it from Orbit instead.
Comment 3 Jan Bartel CLA 2011-08-10 20:33:30 EDT
Hugues,

I've changed jetty-8 jetty-distribution to use the jsp-2.2 jar from Orbit. I assume that contains the JDTJavaCompiler fix to allow it to work with OSGi?

Jan
Comment 4 Hugues Malphettes CLA 2011-08-10 20:39:23 EDT
(In reply to comment #3)
> Hugues,
> 
> I've changed jetty-8 jetty-distribution to use the jsp-2.2 jar from Orbit. I
> assume that contains the JDTJavaCompiler fix to allow it to work with OSGi?
Yes it does. I have packaged in orbit what we described in the CQ: a patched jsp-2.2 jar. (the patch was committed into glassfish's svn in a newer build).
Hugues
> 
> Jan
Comment 5 Hugues Malphettes CLA 2011-10-02 21:40:41 EDT
This bug should have been marked as resolved before 8.0.0 was released.