[sakai2-tcc] Java 1.6 and Sakai 2.9

[Steve Swinsburg]

I am in favour of your proposed date:

> between Wed-Fri, 1-3 December


cheers,
Steve



On 20/11/2010, at 3:13 AM, Anthony Whyte wrote:

> Next Tuesday I plan to reconfigure the purepoms compiler plugin to compile with 1.6 (locally) and see how the indies behave when I compile them.  If they compile without complaint when I run
> 
> mvn compile
> 
> I'll test the rest of trunk.  If trunk behaves then perhaps we set the date between Wed-Fri, 1-3 December.  The date should be coordinated with Chris--not sure if Nightly2 build scripts require any adjustment.
> 
> I plan to use version 2.3.2 of the compiler plugin (and specify the version in the <plugin> entry).
> 
> 
> <plugin>
> 				<inherited>true</inherited>
> 				<groupId>org.apache.maven.plugins</groupId>
> 				<artifactId>maven-compiler-plugin</artifactId>
> 				<configuration>
> 					<source>1.6</source>
> 					<target>1.6</target>
> 				</configuration>
> 			</plugin>
> 
> Cheers,
> 
> Anth
> 
> 
> On Nov 19, 2010, at 10:55 AM, Seth Theriault wrote:
> 
>> Matthew Jones wrote:
>> 
>>> As mentioned on the source install guide, "Oracle's Sun Java SE 
>>> 6<http://java.sun.com/javase/6/>, a.k.a Java 1.6, is the 
>>> preferred version to use with Sakai 2.7." [1] However there is 
>>> still some confusion about what this means. As we know Java 5 
>>> is nearly a year now past the End of Life (11/09) and also 
>>> harder to find for new people looking for it.
>> 
>> We definitely need to clarify this for the 2.8 release. If no QA 
>> servers are running or building under 1.5 -- I am ignoring the 
>> target versions discussion for now -- then we can be more 
>> confident in making a statement along the lines of "we recommend 
>> 1.6 and that's what this thing was QA'd on."
>> 
>> I have sent somemail to the qa-admins list about the use of 1.6.
>> 
>>> I agree with Seth that we should:
>>> 
>>> * Make the decision to switch the compilation for trunk (2.9) to 1.6. Sakai
>>> after this version will no longer be guaranteed to be compatible with
>>> JDK/JRE 1.5 and apis/methods/libraries specific to 1.6 could be used if
>>> necessary.
>> 
>> Anyone have a suggestion for a date to move over definitely to 
>> 1.6 in trunk? We could just announce a hard cutover to 
>> identify/re-confirm the problem points that exist even with the 
>> workarounds.
>> 
>> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20101122/91bceaf3/attachment.html