[sakai2-tcc] Are we supporting Java 1.5 for 2.8?

Jean-Francois Leveque jean-francois.leveque at upmc.fr
Mon Feb 21 02:57:32 PST 2011


Let's make this a 2.9 blocker and work on this at least as soon as 2.8.0 
is released.

Who creates the issue in JIRA?

Cheers,
J-F

On 19/02/2011 01:15, Steve Swinsburg wrote:
> Yep lets get any required modifications committed into trunk, and enforce 1.6 as soon as possible so we can iron anything out early.
>
> cheers,
> Steve
>
>
> On 19/02/2011, at 2:02 AM, Anthony Whyte wrote:
>
>> I agree with this approach.  We are a bit late in the releasecycle to require Java 6 (which will force us to patch the code).  I do think we should make the required changes to trunk as soon as possible.
>>
>> Cheers,
>>
>> Anth
>>
>> On Feb 18, 2011, at 9:43 AM, John Bush wrote:
>>
>>> This is exactly what I would like to see.  Let's just get it building,
>>> which it will after a few things aren't merged.  Its working for me
>>> now with the patches from yesterday.  I think its just too late to
>>> make the decision to force people off of 1.5, its clear from this
>>> discussion that we've haven't set that expectation yet.  Then for 2.9
>>> its a different story.
>>>
>>> On Fri, Feb 18, 2011 at 7:39 AM, David Horwitz<david.horwitz at uct.ac.za>  wrote:
>>>> My recommendation:
>>>>
>>>> 2.8: recommend 1.6 - code compiles in 1.5
>>>> 2.9: require 1.6 - no guarantee  that code will compile/run in 1.5
>>>>
>>>> D
>>>>
>>>> On 02/18/2011 04:32 PM, Seth Theriault wrote:
>>>>> Anthony Whyte wrote:
>>>>>
>>>>>
>>>>>> If we want to drop 1.5 then we need to make sure that the
>>>>>> code compiles after adjusting Maven's compiler plugin
>>>>>> settings from 1.5 to 1.6.  Last time I checked (early
>>>>>> December) the kernel failed to build due to an issue with
>>>>>> kernel util's validater.java due to "unmappable character
>>>>>> for encoding UTF-8 (53 cases)."
>>>>>>
>>>>> I think we should be clear about what we want to do for 2.8.
>>>>>
>>>>> There is a difference between telling people to use 1.6
>>>>> (while maintaining the 1.5 source and targets) and forcing the
>>>>> use of 1.6 (by changing them).
>>>>>
>>>>> Given that we are late in the cycle and we know that (from QA)
>>>>> that the current 2.8 code can be built and run in 1.6 --
>>>>> albeit with 1.5 source and targets -- I think we should just
>>>>> emphatically state the need to use 1.6, rather than force it.
>>>>>
>>>>> Seth
>>>>>
>>>>> _______________________________________________
>>>>> sakai2-tcc mailing list
>>>>> sakai2-tcc at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>>>
>>>> _______________________________________________
>>>> sakai2-tcc mailing list
>>>> sakai2-tcc at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>>>
>>>
>>>
>>> -- 
>>> John Bush
>>> 602-490-0470


More information about the sakai2-tcc mailing list