Maybe you want to be the first on your block to make a patch for the new kernel. So you need to check out, modify, and compile the new kernel. You may even want to test your changes in Tomcat :)
When Ian wakes up, he might tell me that I am completely wrong – but this worked:
cd ~/dev/sakai-trunk
svn co https://source.sakaiproject.org/svn/kernel/trunk kernel
I check this out into the same directory as sakai – not inside of the sakai directory – so ls looks like this
charles-severances-macbook-air:sakai-trunk csev$ pwd
/Users/csev/dev/sakai-trunk
charles-severances-macbook-air:sakai-trunk csev$ ls -ld kernel sakai
drwxr-xr-x 23 csev staff 782 Jul 30 14:39 kernel
drwxr-xr-x 73 csev staff 2482 Jul 30 15:21 sakai
Then I go into the kernel directory and type this:
mvn -Dmaven.test.skip=true -Dmaven.tomcat.home=/Users/csev/dev/sakai-trunk/apache-tomcat-5.5.23/ clean install sakai:deploy
This is the same thing I type to compile sakai.
It compiles kernel – puts it into my maven repo and then puts it right into my Tomcat!
Voila!

I am back up with K1 – it was not so hard – My instructions are a little different than Ian’s because I use vi and no debugger. A key here is that you don’t have to switch to how Ian does his tomcat stuff – just for K1 – I did my normal process (different than Ian’s) and it all still came up fine – so whatever your process is – it should work as well.
I include my steps
Whacked the repo (per Ian)
rm -rf ~/.m2/repository/org/sakaiproject
Whacked my tomcat
rm -rf ~/dev/sakai-trunk/apache-tomcat-5.5.23/
Unzipped a new fresh tomcat 5.5.23
cd ~/dev/sakai-trunk/
curl -O http://source.sakaiproject.org/mirrors/ibiblio/maven/tomcat/zips/apache-tomcat-5.5.23.zip
unzip -q apache-tomcat-5.5.23.zip
chmod +x apache-tomcat-5.5.23/bin/*.sh
Clean check out
svn co https://source.sakaiproject.org/svn/sakai/trunk/ sakai
Full compile attempt – Failed with the following message
[INFO] Failed to resolve artifact.
GroupId: org.sakaiproject
ArtifactId: master
Version: SNAPSHOT
Reason: Unable to download the artifact from any repository
org.sakaiproject:master:pom:SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
Do the master thing – as per Ian:
cd sakai/master/
mvn install
— BUILD Successful
Full compile:
mvn -Dmaven.test.skip=true -Dmaven.tomcat.home=/Users/csev/dev/sakai-trunk/apache-tomcat-5.5.23/ clean install sakai:deploy
Started tomcat – navigate to http://localhost:8080/
Viola – Sakai is back with K1
Now – I am wondering where site code went… Hmmm. I was busily working on SAK-13482 and was ready to check in – when I realized the world had just changed out from under me – that will wait until Ina gets back.
NICE WORK IAN!

Our trunk is now reorganized to define a kernel – this will be a few days of angst – the contrib folks will need to react – Ian has provided a nice XSLT to get the pom.xml files fixed with minimal pain.
This will also make the 2-5-x branch management a little more dicey for 2-5-3, etc.
Progress is needed and this is a great time to take this plunge – when we have 2.5.2 in hand – and the 2-5-x branch is in pretty good shape – and we have some time before the 2.6 code freeze.
Folks not working on the deep bits of Sakai – might want to avoid doing an update for a few days – if you are working in the new Kernel area – you pretty much need to update and help figure out the new way.
Here is Ian’s note.
Again – thanks for the fine work, Ian!

Continue reading →