Shibboleth Developers

["Howard Gilbert" <>]

The current release of Mockrunner 0.3.6 now creates some JSP 2.0 objects
that can be used for JSP testing. We don't currently use this, but the
objects are created unconditionally. This requires some JSP 2.0 (EL) classes
in the classpath. Possible solutions (in no particular order) are:

Freeze on 0.3.5 and give up bug fixes and improvements. [I don't like this.]

Change the Eclipse classpath (and any JUnit test classpath for the
integration tests) to use current Servlet/JSP libraries and cross our
fingers and promise not to use Servlet features not supported by the oldest
release we claim to support.

Run the current Servlet API JAR file first, but then add the JSP 2.0 JAR
file second in the search path. [This works but was rejected on the last
phone call as unacceptable. I keep it in just to be comprehensive.]

Modify Mockrunner to fix the problem (comment out four lines we don't use),
then use our version of Mockrunner instead of the real one. Won't be the
first time we struggled with third party libraries. 

Create one modified Mockrunner class source in our project test source with
the fixes. It will come first in the classpath search and override the
corresponding class in the 0.3.6 JAR. 

Create a separate test case project dependent on the shib Java project but
with its own classpath that uses the later Servlet library.

I sorta like the last choice (separate project). The Integration tests
aren't a standard part of the distribution, so having yet another odd
project in the CVS isn't a problem for the newbie.