[Building Sakai] How to modify K1?

[Lydia Li]

Thanks again for everyone's  help on and off the list.

Not sure if this would be helpful to others who haven't been following 
2.6 too closely like me.  After trying out everyone's suggestions and 
wiping out my maven repo, rebuilding from scratch many times, it turned 
out that I was getting the error not because of the wrong kernel I was 
using.   Like I said in the original email,  I did see my modified 
db-components.xml deployed in tomcat.   My problem was actually that I 
didn't specify the sakai-configuration.xml file under tomcat/sakai, so 
it kept using the default.sakai.properties and that had the dbcp 
configurations.   After I added the file and configured the location of 
my sakai.properties,  everything came up just  fine.  Just thought to share.

Thanks again!
Lydia


Lydia Li wrote:
> Anthony and Matthew,
>
>     Thanks for the tips!  I'll give it a try!
>
>
> Lydia
>
>
>
> Anthony Whyte wrote:
>   
>> Lydia--the Sakai 2.5 series does not bind to the Kernel K1 project and 
>> never will.  Sakai core services (e.g., authz, content, userdirectory, 
>> etc.) were repackaged as the kernel for Sakai 2.6 and 2.7.  Sakai 
>> 2.6.x currently binds to the stable K1 1.0.6 release since it is 
>> anticipated that a fair number of schools will choose to run the x 
>> branch in production and doing so while binding to SNAPSHOT artifacts 
>> of the kernel such as 1.0.7-SNAPSHOT (which can and do get refreshed 
>> in the repo) would introduce into your production environment an 
>> unacceptable level of code instability with respect to low-level Sakai 
>> services.
>>
>> If you want to make changes to K1 locally, do what Matt suggests.  For 
>> 2.6.x check out the latest release or trunk or the 1.0.x branch, 
>> although again bear in mind that the latter are regularly updated and 
>> that the corresponding repo artifacts also get refreshed.  Depending 
>> on what you need to do you can change the <version> and then hack the 
>> code.  Then do a
>>
>> mvn clean install
>>
>> to populate your local repo (I like to delete 
>> .m2/repository/org/sakaiproject/kernel first so that when I perform a 
>> Sakai build I can ensure that only one set of kernel dependencies gets 
>> deployed).  Finally, make sure the Sakai /master/pom.xml 
>> <sakai.kernel.version> property is updated to your new K1 <version>.
>>
>> Then perform a Sakai build:
>>
>> mvn clean install sakai:deploy
>>
>> and test your changes.
>>
>>
>> General info regarding the Kernel can be found here:
>>
>> http://bugs.sakaiproject.org/confluence/display/REL/Kernel+1+(K1)
>>
>> More specific info relative to issues addressed in each release can be 
>> found here:
>>
>> http://bugs.sakaiproject.org/jira/browse/KNL?report=com.atlassian.jira.plugin.system.project:versions-panel 
>>
>>
>> Cheers,
>>
>> Anth
>>
>>
>>
>> On Apr 30, 2009, at 8:34 PM, Lydia Li wrote:
>>
>>     
>>> Ray,
>>>    Thanks for your quick reply.
>>>   A quick question, I checked in my sakai 2.6.x/master/pom.xml and it
>>> has <sakai.kernel.version>1.0.7-SNAPSHOT</sakai.kernel.version>
>>>   which is the same as the version  specified in my kernel 1.0.x
>>> checkout.
>>>   Where does it specify sakai 2.5.x using 1.0.6 snapshot?
>>>
>>>    Sorry if the answer is too obvious... I've been in the 2.4.x world
>>> for too long.
>>>
>>> thanks,
>>> Lydia
>>>
>>>
>>> Ray Davis wrote:
>>>       
>>>> Sakai 2.6.x was building against kernel 1.0.6-SNAPSHOT and is now
>>>> building against kernel 1.0.6. Meanwhile the kernel-1.0.x branch has
>>>> moved on to 1.0.7-SNAPSHOT. So it could be that your customized K1
>>>> build is generating different files than your customized Sakai build
>>>> is deploying.
>>>>
>>>> Keeping the two projects in sync locally is a bit of a challenge. I
>>>> see we've just gone off the rails here, too....
>>>>
>>>> Best,
>>>> Ray
>>>>
>>>> On 4/30/2009 4:35 PM, Lydia Li wrote:
>>>>         
>>>>> Hi,
>>>>>
>>>>>     We are starting to work on upgrading our local Sakai 2.4.x to
>>>>> 2.6.x here at Stanford.   One thing we have to modify is the
>>>>> db-components.xml in kernel to use c3p0 instead of dbcp.  I checked
>>>>> out kernel 1.x , modified the file, deleted everything under
>>>>> .m2/repository/org/sakaiproject/kernel, then compiled and deployed
>>>>> kernel.  I also rebuilt the entire Sakai in a clean tomcat.  I could
>>>>> see my changes in
>>>>> tomcat/components/sakai-kernel-component/WEB-INF/db-components.xml ,
>>>>> but when I started tomcat it kept complaining about not finding the
>>>>> expected dbcp properties (such as:  No property 'url' found).   It
>>>>> seems to be still looking for the out of the box 1.0.7-SNAPSHOT.jar
>>>>> with dbcp somewhere.   I must be missing some other places that I
>>>>> needed to modify for my tomcat to pick up my changes.    What else do
>>>>> I need to do?     Are there any documentation on how to make local
>>>>> modification to K1?    I couldn't find it on Confluence or the
>>>>> sakai-kernel google group.
>>>>> thanks,
>>>>> Lydia
>>>>>           
>>> _______________________________________________
>>> 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/20090501/69d87b4c/attachment.html