[MYFACES-2990] JDTCompiler wants access to more classes in osgi

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.3-SNAPSHOT
• Fix Version/s: 2.0.3
• Component/s: General
• Assignee: Leonardo Uribe
• Reporter: David Jencks
• Created: 02/Dec/10 00:36
• Updated: 14/Dec/10 01:01
• Resolved: 02/Dec/10 16:29

Description

Running the tck we get into a bunch of problems with superclasses of exposed classes not being visible to the eclipse JDTCompiler used to compile jsps. A typical error looks like...

11-30-2010 17:23:11: TRACE: [WIRE] - << "Caused by: org.apache.jasper.JasperException: Unable to compile class for JSP: [\n]"
11-30-2010 17:23:11: TRACE: [WIRE] - << "[\n]"
11-30-2010 17:23:11: TRACE: [WIRE] - << "An error occurred at line: 1 in the generated java file[\n]"
11-30-2010 17:23:11: TRACE: [WIRE] - << "The type org.apache.myfaces.shared_impl.taglib.UIComponentELTagBase cannot be resolved. It is indirectly referenced from required .class files[\n]"

I don't know how the eclipse compiler is tying itself in these knots, I guess it assumes that the classloader you give it can load by name all superclasses of accessible classes. It would be better to figure out either how to give the compiler such a classloader or figure out how to remove this assumption from the compiler, but it seems more practical at the moment to just export the needed superclasses.