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

[Steve Swinsburg]

Yep, I've updated 2.8.x master to build against 1.2.3-SNAPSHOT and all is well. This raises the question of whether or not the Sakai branches (e.g. 2.8.x) should bind against the branch of the kernel (e.g. 1.2.3-SNAPSHOT).



On 03/08/2011, at 10:38 PM, Bryan Holladay wrote:

> well ignore my last comment there... I changed it locally to 1.2.3-SNAPSHOT to build and forgot.
> 
> On Wed, Aug 3, 2011 at 8:29 AM, Bryan Holladay <holladay at longsight.com> wrote:
> Thanks Steve... I thought that the core sakai tools would be ok since 2.8.x's master pom points to 1.2.3-SNAPSHOT and I committed the kernel part to 1.2.x.  So I just reverted the msgcntr branch b/c it points to a tagged release of kernel.
> 
> Thanks,
> Bryan
> 
> 
> On Wed, Aug 3, 2011 at 1:44 AM, Anthony Whyte <arwhyte at umich.edu> wrote:
> I expect to push a kernel-1.2.3 release later today, Wednesday, 3 August.  Earlier I talked to Bryan about SAK-16568, r96168 and recommended that he revert the tool commits to 2.8.x to restore branch stability in the interim.
> 
> Also, the kernel commit merged to 1.2.x as part of r96168 and its companion trunk commit of r95924 should either be tracked as part of KNL-737 or a new KNL ticket should be filed for it.  SAK-16568 should be linked to the KNL ticket as "dependent on" rather than "related to" as I believe is currently the case.
> 
> Cheers,
> 
> Anth
> 
> 
> 
> 
> 
> 
> 
>  
> 
> 
> On Aug 3, 2011, at 12:48 AM, 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
>>>> 
>>> 
>> 
>> _______________________________________________
>> 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/20110803/f2052eb5/attachment.html