[Building Sakai] nightly2

Bryan Holladay holladay at longsight.com
Tue Oct 8 05:41:04 PDT 2013


I updated Delegated Access a week ago so that it would build against trunk,
please don't remove that.  (and as Matt said, Hierarchy should build, which
Delegated Access depends on).

Thanks,
Bryan


On Mon, Oct 7, 2013 at 5:57 PM, Matthew Jones <matthew at longsight.com> wrote:

> I removed these ones I mentioned from the experimental pom.
>
>
> On Mon, Oct 7, 2013 at 5:52 PM, Matthew Jones <matthew at longsight.com>wrote:
>
>> That sounds right. I think we'll have to remove the ones that fail to
>> build against trunk until/unless they are updated and still desired.
>>
>> Assignment2 currently is the one stopping the build but most likely most
>> of them won't build/work correctly under 2.10 because of the hibernate and
>> spring changes. (Let alone the pom changes) Someone with A2 commit could
>> fix this.
>>
>> Signup builds and has a 2.10 parent
>> Dashboard builds and has 2.10 parent
>> Evaluation has a 2.8.2 parent and has a test failure for me (but builds
>> skipping tests) though seems like it might fail at runtime without the
>> correct dependencies and a profile for 2.10.
>> -  Hierarchy is standalone and will still build
>> Clog and roster 2 have a 2.8 parent and build though seems like it might
>> fail at runtime without correct dependencies
>> Endorsed should still work
>>
>> Remove hybrid and I don't know what formbuilder and reports are.
>>
>> So I'd comment assignment2, hybrid, forumbuilder, reports and it should
>> be back up?
>>
>>
>> On Mon, Oct 7, 2013 at 5:37 PM, Thomas, Gregory J <gjthomas at iu.edu>wrote:
>>
>>>  I think it got lost in the shuffle of the last nightly2 email thread,
>>> but there's not a quick answer on fixing this particular instance (which is
>>> the experimental build server)
>>>
>>> The indie tools that are pulled in haven't had the same conversion process done to them that the semi-recent move to get trunk to a monolithic build (https://jira.sakaiproject.org/browse/SAK-23907) have had done.  These include (but not fully checked individually for issues):
>>>
>>> assignment2 https://source.sakaiproject.org/contrib/assignment2/trunk
>>> clog https://source.sakaiproject.org/contrib/clog/trunk
>>> clogdashboardintegration https://source.sakaiproject.org/contrib/lancaster.ac.uk/clogdashboardintegration/trunk
>>> dashboard https://source.sakaiproject.org/contrib/dashboard/trunk
>>> delegatedaccess https://source.sakaiproject.org/contrib/delegatedaccess/trunk
>>> endorsed https://source.sakaiproject.org/contrib/endorsed/trunk
>>> evaluation https://source.sakaiproject.org/contrib/evaluation/trunk
>>> formbuilder https://source.sakaiproject.org/contrib/ucf/formbuilder/trunk
>>> hierarchy https://source.sakaiproject.org/contrib/caret/hierarchy/trunk
>>> hybrid https://source.sakaiproject.org/svn/hybrid/trunk
>>> reports https://source.sakaiproject.org/svn/reports/trunk
>>> roster2 <https://source.sakaiproject.org/svn/reports/trunkroster2> https://source.sakaiproject.org/contrib/roster2/trunk/
>>> signup https://source.sakaiproject.org/contrib/signup/trunk/
>>>
>>> The options are:
>>>
>>>
>>>    1.
>>>
>>>    Remove individual tools from experimental
>>>
>>>    2.
>>>
>>>    Have a similar process done on cleaning up pom.xml files like SAK-23907 has done
>>>
>>>
>>>
>>>  Option 2 is tricky since I don't know ramifications of editing pom
>>> files in each code base.  It's possible some institutions could be using
>>> some of these from their respective trunk repositories.  Longer term, yeah,
>>> I think it would be great to have contrib tools be organized in a similar
>>> way that's been done in SAK-23907, but that will take some time to talk
>>> with contrib tool owners to be ok with the changes.
>>>
>>>  I could remove all of these for now if we just want the server to be
>>> back up, but that would basically mean the server is mostly identical with
>>> nightly trunk. :)  http://nightly2.sakaiproject.org:8082/portal
>>>
>>>  Greg
>>>
>>>
>>>   From: Steve Swinsburg <steve.swinsburg at gmail.com>
>>> Date: Monday, October 7, 2013 8:01 AM
>>> To: Adam Marshall <adam.marshall at it.ox.ac.uk>
>>> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
>>> Subject: Re: [Building Sakai] nightly2
>>>
>>>   There is an extra comma in the SQL:
>>>
>>> java.sql.SQLException: Unexpected token: ) in statement [ CREATE TABLE CONTENT_RESOURCE_BB_DELETE ( RESOURCE_ID VARCHAR (255) NOT NULL, BODY BINARY, )]
>>>
>>> I've fixed and committed at r130199 against KNL-309
>>>
>>>  I also question the oracle scripts using LONG RAW datatype. They
>>> should really be using a CLOB or BLOB. I'll raise that in the Jira.
>>>
>>>  cheers,
>>> Steve
>>>
>>>
>>>  On 07/10/2013, at 10:34 PM, Adam Marshall <adam.marshall at it.ox.ac.uk>
>>> wrote:
>>>
>>> I hate to raise this again but:
>>> http://nightly2.sakaiproject.org:8085/portal is still broken
>>>
>>> adam
>>>
>>> --
>>> Dr A C Marshall, WebLearn Service Manager, University of Oxford.
>>> IT Services, 13 Banbury Rd, Oxford. OX2 6NN.
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20131008/566ff907/attachment.html 


More information about the sakai-dev mailing list