tail -f logs/catalina.out | grep -v INFOwhich doesn't display all the INFO messages but still shows me anything serious, and all the internal tomcat messages about how the startup is progressing. I know I could change the logging (log4j) but this is a simple trick which still allows me to look back at the info messages to check things.
Tuesday, May 29, 2007
Friday, May 25, 2007
tomcat-users.xmlas I didn't have any existing users I wanted to keep.
After a quick scan of the
grouper-ui/build.properties file I attempted to build the UI with
ant ui and selected option 6 (war) however this fell over with an ugly ant error. Looking at the
build.xml it seemed to be failing on the <propertyfile> task. A quick google and it seems this is an optional task, from previous experience I knew that the nice Ubuntu people split off the optional ant tasks into a seperate packages and sure enough that was missing on my system. An
apt-get later and I had the ant build successfully running.
I copies the newly created WAR into Tomcat and started it up. 14 seconds later I could access the Grouper UI. After a delay I realised that all I had was a redirect to populateIndex.do and a blank page. Then I remembered a mention at the start of the document saying I needed an HSQL database to be running. As it turns out this is actually reasonably easy, just ant db at the toplevel of the quickstart. Then a trip back to the webserver and yey, a working grouper installation. Now time for a little play.
Tuesday, May 22, 2007
- Get source checkout from svn of 2.4.0
- Set maven.repo.remote in master/build.properties
- Check build works with maven bld
- Get patches used on 2.3.1 release
- Apply patches to login-tool and providers and fix rejections
- maven cln bld
- maven sakai:deploy-zip
- Copy sakai.tar.gz to server
- Stop existing tomcat and move out of the way
- Expand a clean tomcat 5.5.23
- Copy across conf/server.xml
- Copy across sakai folder from 2.3.1
- Copy across mysql connector from 2.3.1
- Upgrade the schema
- Copy across /portal redirection
- Start up tomcat
Monday, May 21, 2007
Maybe the version of maven 2 artifacts should be dev by default, rather than M2, to match maven 1? What I'm not yet sure of is why you would ever want more than copy of a particular JAR in a classloader, so maybe the version shouldn't be used in the filename when the deployment is made. Although in production it is useful to have the versions for working out what versions of a file you have.