Move jstl library out of /shared/lib and rebundle in project webapps

Description

The jstl-1.1.2.jar is currently deployed to shared, preventing developers from using new versions of jstl in their tool projects. Steps for removal involve retiring the jstl-shared-deploy pom and then rebundling the jstl jar in project webapps, plus testing.

./deploy/shared/pom.xml: <artifactId>jstl</artifactId>
./gradebook/app/business/pom.xml: <artifactId>jstl</artifactId>
./gradebook/app/sakai-tool/pom.xml: <artifactId>jstl</artifactId>
./gradebook/app/standalone-app/pom.xml: <artifactId>jstl</artifactId>
./gradebook/app/ui/pom.xml: <artifactId>jstl</artifactId>
./gradebook/testservice-tool/pom.xml: <artifactId>jstl</artifactId>
./help/help-tool/pom.xml: <artifactId>jstl</artifactId>
./jobscheduler/scheduler-tool/pom.xml: <artifactId>jstl</artifactId>
./jsf/jsf-tool-sun/pom.xml: <artifactId>jstl</artifactId>
./jsf/myfaces-tool/pom.xml: <artifactId>jstl</artifactId>
./jstl-shared-deploy/pom.xml: <artifactId>jstl</artifactId>
./kernel/pom.xml: <artifactId>jstl</artifactId>
./metaobj/metaobj-tool/tool/pom.xml: <artifactId>jstl</artifactId>
./osp/common/tool/pom.xml: <artifactId>jstl</artifactId>
./osp/glossary/tool/pom.xml: <artifactId>jstl</artifactId>
./osp/jsf/example/pom.xml: <artifactId>jstl</artifactId>
./osp/portal/tool/pom.xml: <artifactId>jstl</artifactId>
./osp/presentation/tool/pom.xml: <artifactId>jstl</artifactId>
./osp/presentation/tool-lib/pom.xml: <artifactId>jstl</artifactId>
./osp/wizard/tool/pom.xml: <artifactId>jstl</artifactId>
./osp/wizard/tool-lib/pom.xml: <artifactId>jstl</artifactId>
./rwiki/rwiki-tool/tool/pom.xml: <artifactId>jstl</artifactId>
./samigo/samigo-app/pom.xml: <artifactId>jstl</artifactId>
./sections/sections-app/pom.xml: <artifactId>jstl</artifactId>
./tool/tool-tool/su/pom.xml: <artifactId>jstl</artifactId>
./user/user-tool-admin-prefs/admin-prefs/pom.xml: <artifactId>jstl</artifactId>
./user/user-tool-prefs/tool/pom.xml: <artifactId>jstl</artifactId>

Activity

Show:

Anthony Whyte June 30, 2011 at 4:58 AM
Edited

Note Aaron Zeckoski's comments in regarding the need to place the jstl jar in the same place as the spring-webmvc jar:

"Unfortunately, tools that use Spring MVC cannot work unless jstl is in the same location as the spring jars for the spring web stuff. If we were to split up the spring jars this might be an option but for now we are stuck with this in shared if there is an app which uses spring mvc in sakai. . . .

We should either close this out or split spring jars so that spring front-end jars are deployed into the tools themselves."

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Created June 30, 2011 at 4:49 AM
Updated October 4, 2013 at 1:08 PM
Resolved August 27, 2011 at 3:22 AM