Have the kernel deploy the JSTL jar to $CATALINA_HOME/shared-lib

Currently we have a pom that deploys the jstl jar to shared/lib

https://source.sakaiproject.org/svn/sakai/trunk/jstl-shared-deploy/pom.xml

I think we should eliminate this pom and simply have the kernel deploy the jstl jar to shared/lib. I recognize it violates best practice regarding dependency management (i.e., including dependency declarations not required by a project should be avoided) but I think it an acceptable exception in this case.

Rationale

1. Arguably, jstl should never have been deployed to shared/lib and instead been bundled up with the tools that need it, but Aaron notes that no doubt contrib tools have come to rely on it in shared/lib so getting it out (an easy task for core tools) is I think a non-starter.

2. Having the JSF project deploy it to shared/lib while meeting a necessary condition for JSF tools fails the sufficiency test since the JSP tag lib can both be employed in a non-JSF context and is required by certain builds such as -Pcafe and -Pframework (does anyone actually use this build any more?) that exclude the Sakai JSF project.

3. The kernel deploys a number of jars to shared/lib such as spring-webmvc that it is not dependent upon. I assume in such cases convenience trumps the purity inherent in best practice. Whatever the case, I think having the kernel deploy jstl a defensible exception.

Core projects with a jstl dependency: gradebook, help, jobscheduler, jsf, metaobj, osp, rwiki, samigo, sections, tool, user.

4. Streamlining our build process and eliminating poms where it makes sense is a good thing.

The jstl dependency would be added to both the kernel assembly and shared poms.

<dependency>
<groupId>javax.servlet</groupId>
<artifactId>jstl</artifactId>
<version>1.1.2</version>
<scope>compile</scope>
</dependency>