[Building Sakai] 2.6.x build is broken

[David Horwitz]

on a related note nightly2 seems dead ...

D

On 05/12/2010 01:42 PM, Jean-Francois Leveque wrote:
> Should we have a policy to deal with broken builds?
>
> Some time ago, I broke the 2.5.x build and I broke trunk not so long 
> ago. Sometimes doing things quickly leads to a broken build.
>
> How long do we want trunk, the next version branch or a maintenance 
> branch to have a broken build (time may differ in each case)?
>
> Should a build task force across time zones be ready to get builds back 
> to working?
>
> A build can even be partly unusable without the build been broken.
>
> How often should we run the expected automated functional testing on builds?
>
> Jean-Francois
>
> Steve Swinsburg a écrit :
>   
>> Hi all,
>>
>> The 2.6.x build is broken:
>>
>> [ERROR] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Compilation failure
>> /Users/steve/dev/sakai/src/2.6.x/sam/samigo-services/src/java/org/sakaiproject/tool/assessment/facade/PublishedAssessmentFacadeQueries.java:[119,7] org.sakaiproject.tool.assessment.facade.PublishedAssessmentFacadeQueries is not abstract and does not override abstract method getPublishedAssessment(java.lang.Long,boolean) in org.sakaiproject.tool.assessment.facade.PublishedAssessmentFacadeQueriesAPI
>>
>> Due to:
>> http://jira.sakaiproject.org/browse/SAM-696
>>
>> >From the commits, the trunk and branch merges don't match and the branch is missing a method.
>>
>>
>> Steve
>>     
> _______________________________________________
> 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"
>