[Building Sakai] Entity References Broken During Site Import: Solution Vote (KNL-737 or SAK-16568)

[Steve Swinsburg]

I've fixed the 2.8.x build by binding it to 1.2.3-SNAPSHOT. This is a stopgap until we decide either way as to a solution (continue to bind branches to kernel snapshots or release 1.2.3).

https://jira.sakaiproject.org/browse/SAK-16568

cheers,
Steve



On 03/08/2011, at 2:48 PM, Steve Swinsburg wrote:

> FYI, this has broken the 2.8.x branch (in announcements) since it binds to kernel 1.2.2 and the required interface in the kernel is not in the 1.2.2 tag (it is in 1.2.3-SNAPSHOT).
> 
> So we either need a release of kernel 1.2.3 or for 2.8.x to bind to a snapshot of the kernel.
> 
> 
> 
> 
>> 
>> 
>> On 29/07/2011, at 2:04 AM, Bryan Holladay wrote:
>> 
>>> Any -1 votes from the community to putting these into trunk (after I make the API changes suggested by Aaron earlier)?
>>> 
>>> -Bryan
>>> 
>>> 
>>> On Thu, Jul 28, 2011 at 11:59 AM, Matthew Buckett <matthew.buckett at oucs.ox.ac.uk> wrote:
>>> On Thu, Jul 28, 2011 at 4:39 PM, Bryan Holladay <holladay at longsight.com> wrote:
>>> > So it sounds like it may be a good idea to mix parts of KNL-737 and
>>> > SAK-16568.  Have KNL-737 do all it's resources magic and use SAK-16568 to
>>> > handle entity references inside tools.  Would this be feasible/logical?
>>> 
>>> Yep, sound good.
>>> 
>>> --
>>>   Matthew Buckett
>>>   VLE Developer, LTG, Oxford University Computing Services
>>> 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110803/81d4108a/attachment.html