[cle-release-team] Remaining issues on Tomcat 7

[Anthony Whyte]

Why don't we schedule a call for Monday.  I can set up a calliflower call for folks to call in.  I will be calling in from Amsterdam.

Any preferences regarding time.  If Monday is no good suggest another date.

Cheers,

Anth


On Sep 23, 2011, at 11:05 AM, Matthew Jones wrote:

> Tomcat 7 was voted to be a requirement for 2.9, we're no longer supporting 5.5, and it will be EOL shortly after 2.9 is released anyway.
> 
> https://confluence.sakaiproject.org/display/TCC/2011+TCC+Voting+Summary
> 
> Nightly is running on Tomcat 7 and these issues should be fixed in trunk and if they're not they will just be fixed there for 2.9. AFIAK no core tools are broken still on nightly.
> 
> The artifact that Chuck Hedrick mentioned on the Jira looks to be available in the repository now for 7.0.21.
> 
> http://search.maven.org/#artifactdetails%7Corg.apache.tomcat%7Ctomcat-catalina%7C7.0.21%7Cjar
> 
> My question was more on *who* would tag the alpha, and whether we were going to virtually meet to talk about it or not.
> 
> -Matthew
> 
> On Fri, Sep 23, 2011 at 9:19 AM, David Horwitz <david.horwitz at uct.ac.za> wrote:
> Yep
> 
> 
> On 09/23/2011 03:12 PM, Anthony Whyte wrote:
>> 
>> That translates into all JSF tools at a minimum needing to bundle up commons-el in their webapp. 
>> 
>> Anth 
>> 
>> On Sep 23, 2011, at 8:33 AM, David Horwitz wrote:
>> 
>>> and almost forgot commons-el is no longer marked a provided by the kernel ...
>>> 
>>> D
>>> 
>>> On 09/23/2011 02:31 PM, David Horwitz wrote:
>>>> 
>>>> As far as I know the commons-el jar does not need to be in shared simply not marked as provided (as its no longer in tomcat) so tools that need it package it in their webapp. The webapp is a far better place for commons-el than shared.
>>>> 
>>>> D
>>>> 
>>>> On 09/23/2011 02:26 PM, Maurer, Christopher Wayne wrote:
>>>>> 
>>>>> Folks,
>>>>> Has there been any progress on wrapping up the remaining issues on Tomcat 7?  I wasn't sure if we intended to still target it for the Sakai 2.9 release.  If so, we need to wrap them up asap!
>>>>> To my knowledge, there is a DAV issue and then something about needing to deploy commons-el to shared/lib.
>>>>> 
>>>>> https://jira.sakaiproject.org/browse/SAK-18760
>>>>> 
>>>>> It would be great if we could get those 2 done so we could put out a 2.9 alpha.  Doesn't make sense to do it until then since a bunch of tools are broken.
>>>>> 
>>>>> Chris
>>>>> 
>>>>> _______________________________________________
>>>>> cle-release-team mailing list
>>>>> cle-release-team at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>> 
>>>> _______________________________________________
>>>> cle-release-team mailing list
>>>> cle-release-team at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>> 
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20110923/e81bb7c3/attachment-0006.html