[Building Sakai] JSTL in shared

[Anthony Whyte]

That is already noted in the tickets as a dependency on KNL-757.

Anth


On Jun 30, 2011, at 7:59 AM, David Horwitz wrote:

> Though for mvc projects this depends on moving spring-webmvc out of shared ...
> 
> D
> 
> On 06/30/2011 01:52 PM, Anthony Whyte wrote:
>> 
>> +1 on moving jstl out of shared.  It involves tweeking project poms for a number of core projects (see below).  There is a jstl-shared-deploy pom that we would retire and then a number of poms would need to be tweeked.  It's not a hard job and I am happy to do it.
>> 
>> gradebook
>> help
>> jobscheduler
>> jsf
>> metaobj
>> osp
>> rwiki
>> samigo
>> sections
>> tool
>> user
>> kernel
>> 
>> I've Jira'd it at 
>> 
>> https://jira.sakaiproject.org/browse/SAK-20779
>> https://jira.sakaiproject.org/browse/SAM-1260
>> 
>> Cheers,
>> 
>> Anth
>> 
>> ______________________________________
>> 
>> JSTL dependency declarations 
>> 
>> ./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>
>> 
>> 
>> 
>> 
>> 
>> On Jun 30, 2011, at 6:12 AM, Stephen Marquard wrote:
>> 
>>> Various tools have moved from depending on jstl being in shared to
>>> packaging it themselves.
>>> 
>>>> From JIRA history, specifically
>>> https://jira.sakaiproject.org/browse/SAK-11547 it looks like the
>>> shared dependency was related to Spring MVC, which suggests that once
>>> spring-webmvc is out of shared, jstl could follow.
>>> 
>>> Cheers
>>> Stephen 
>>> 
>>> 
>>> -- 
>>> Stephen Marquard, Learning Technologies Co-ordinator
>>> Centre for Educational Technology, University of Cape Town
>>> http://www.cet.uct.ac.za
>>> Email / IM (Jabber/XMPP): stephen.marquard at uct.ac.za
>>> Phone: +27-21-650-5037 Cell: +27-83-500-5290 
>>> 
>>> 
>>>>>> David Wafula <davidwaf at gmail.com> 6/30/2011 11:55 AM >>> 
>>> Hi all,
>>> Finally discovered jstl-1.1.2.jar is deployed in shared, thus
>>> preventing me
>>> from using newer jstl which  we were hoping to use our tool. What is
>>> the
>>> implication of moving it out of shared, if that is not too much to
>>> ask?
>>> 
>>> -- 
>>> David Wafula
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ###
>>> UNIVERSITY OF CAPE TOWN 
>>> 
>>> This e-mail is subject to the UCT ICT policies and e-mail disclaimer
>>> published on our website at
>>> http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from
>>> +27 21 650 9111. This e-mail is intended only for the person(s) to whom
>>> it is addressed. If the e-mail has reached you in error, please notify
>>> the author. If you are not the intended recipient of the e-mail you may
>>> not use, disclose, copy, redirect or print the content. If this e-mail
>>> is not related to the business of UCT it is sent by the sender in the
>>> sender's individual capacity.
>>> 
>>> ###
>>> 
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>> 
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>> 
>>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110630/288976e2/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110630/288976e2/attachment.bin