[Building Sakai] Email Template Service and Kernel

[Neal Caidin]

Update on this.

On the Sakai Core team call it was determined that the email notification
code was the offending section. So only the email notification part of this
feature is being reverted. The feature is staying in.

Cheers,
Neal





On Fri, Mar 14, 2014 at 12:05 PM, Kirschner, Beth <bkirschn at umich.edu>wrote:

> I'd vote for reverting SAK-24423 in the 10.x branch if it can be done
> cleanly.
>
> - Beth
>
> On Mar 14, 2014, at 9:43 AM, Matthew Jones <matthew at longsight.com> wrote:
>
> > Yeah, that sounds good to me too. But that still leaves this patch. So I
> guess your second point brings up the other decision. Do we revert the
> SAK-24423 feature from 10, leaving it for 11 because of this problem or
> leave it in there hoping that this ETS service has a resolution, which is
> merged into 10 before the release?
> >
> > I don't *think* it would be a lot of work but there's going to be
> minimally pom changes across every tool that uses ETS, so maybe better left
> for 11.
> >
> >
> > On Fri, Mar 14, 2014 at 9:30 AM, Kirschner, Beth <bkirschn at umich.edu>
> wrote:
> > I think it's worthwhile to preserve the concept of a self-contained
> kernel. Adding ETS to the kernel, while keeping the tool outside of the
> kernel makes a lot of sense to me. That said, I'd think starting this work
> in the Sakai 10 branch would be a mistake.
> >
> > - Beth
> >
> > On Mar 14, 2014, at 9:21 AM, Matthew Jones <matthew at longsight.com>
> wrote:
> >
> > > There was an issue that came up that Matthew Buckett noticed that I
> think should have some more attention so I'm putting it out here for some
> feedback.
> > >
> > > https://jira.sakaiproject.org/browse/KNL-1202 - Kernel depends on
> email template service.
> > >
> > > The dependency came about from a commit in
> https://jira.sakaiproject.org/browse/SAK-24423, this change is in Sakai
> 10 as it was in before the cut over. (qa03) We had a discussion on the past
> in https://jira.sakaiproject.org/browse/KNL-484 about whether or not ETS
> should be in kernel, with a few people agreeing. Though on this ticket
> Matthew looks to be in disagreement from the comments and believes that it
> should remain separate.
> > >
> > > Any opinions on this? I believe that if we did add ETS service to
> kernel, we'd still want the ETS tool to be left out, like how content is
> still partially outside of kernel. Otherwise it seems like only way to
> resolve this issue would be to revert
> https://jira.sakaiproject.org/browse/SAK-24423 or rework that patch to
> not send notifications from the kernel (It's doing this in BaseSiteService).
> > >
> > > I don't know even how big a deal it is anymore for monolithic Sakai.
> Is there even an expectation that you should be able to build kernel
> without building everything else? I think maybe kernel should still be a
> special exception, though maybe not.
> > > _______________________________________________
> > > 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/20140326/8438e7c4/attachment.html