[Building Sakai] A kernel branch in sakai?

Jim Eng jimeng at umich.edu
Wed Aug 21 15:35:59 PDT 2013


Thanks, Earle.  Very helpful information.  

Jim


On Aug 20, 2013, at 10:49 AM, Earle Nietzel <enietzel at anisakai.com> wrote:

> Hi Jim,
> 
> 1) When you make changes to kernel you will build and deploy kernel. If there are changes to the kernel api this is only deployed to shared lib and nowhere else. So this is taken care of by step 1.
> 
> 2) Any other projects that import kernel especially components and webapps those projects will continue to use the versions they were shipped/packaged with. So if you make a change in kernel impl and the change was to be used by another project you should rebuild and deploy that other project in order to pick up the change, unless that project does not import kernel artifacts. Most projects typically will import kernel artifacts into the projects component (impl) and or tool (webapp).
> 
> To boil it down a little when I typically make a change to kernel I will build deploy kernel and then right after do the same on the project I was working on even if I didn't make a change to the project in that iteration.
> 
> Keep in mind that any changes made to kernel do affect other projects and you should rebuild all projects at some point.
> 
> Earle
> 
> 
> 
> On Mon, Aug 19, 2013 at 8:03 PM, Jim Eng <jimeng at umich.edu> wrote:
> It's been a while since I've worked in kernel, and I'd appreciate help getting oriented.
> 
> I made a branch from trunk of kernel that I'd like to build and deploy along with trunk of sakai and a new project that will be a client of some parts of my kernel build.  Other parts of sakai are also dependent on parts of kernel where I am working.
> 
> I will need to iterate a bit -- make changes in kernel and changes in this new project and then run them with each other.
> 
> Is there a simple pattern for accomplishing that?  Do I have to shut down sakai, rebuild kernel, rebuild (and deploy) all of sakai, and then restart sakai?  Or are there any useful shortcuts to that process?
> 
> Appreciate any suggestions.
> 
> Jim
> _______________________________________________
> 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/20130821/70443837/attachment.html 


More information about the sakai-dev mailing list