My K1 Experience

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!