[Building Sakai] How to modify K1?

[Matthew Jones]

Here's what I might try:

To make sure it picks up your local kernel changes, modify the version of
kernel. You can either try to use the release plugin, or just run a perl/sed
script to change it to some new name. If you trust that it won't go out to
get the kernel, then just make sure that your kernel matches whats in the
master. The new name I picked was just 1.1-LOCALBUILD. It all compiles but I
haven't tested this in 2.6 yet.

#KERNEL
# Check out the kernel, trunk or whatever tag you want
https://source.sakaiproject.org/svn/kernel/trunk sakaikernel
cd sakaikernel
# Replace the tag names
find . -type f -name '*.xml' |xargs perl -w -i -p -e
's/1.1-SNAPSHOT/1.1-LOCALBUILD/g'

# Install the kernel
mvn install
cd ..

#SOURCE
#Check out the source, trunk or whatever version you want
svn co https://source.sakaiproject.org/svn/sakai/trunk/ sakaitrunk
cd sakaitrunk
#Edit the master, manually or automatically, have to escape .'s and /'s in
regex
find master -name "pom.xml" | xargs perl -w -i -p -e
's/(<sakai\.kernel\.version>).*(<\/sakai\.kernel\.version>)/${1}1\.1-LOCALBUILD${2}/g'

cd ..
#Install it, or maybe run a packdemo or deploy or something
mvn install

I've also been testing out a potentially easier pool configuration change
with jndi data sources that might be easier to switch around to.

-Matthew

On Thu, Apr 30, 2009 at 8:34 PM, Lydia Li <lydial at stanford.edu> 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"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090430/1bf17b92/attachment.html