SnipSnap stirs

I posted a message a few weeks ago asking about the state/availability  
of the SnipSnap source code, and since there was recently a spate of  
postings about moving away from SnipSnap, I thought I'd follow up.

I've got a copy of the fork made by Paulo Abrantes (http://www.pabrantes.net 
), and it compiles cleanly apart from a handful of deprecation  
warnings. (It uses a JAR of Radeox, but I have that in source form as  
well - I've not tried building it yet.)

The build process is geared towards standalone operation using Jetty,  
but it's possible to punt the JARs and configs of an instance into  
Tomcat without too much difficulty; I now have it running in Tomcat 6.  
(It might also be possible to do the initial config from Tomcat as  
well - I didn't try that, and I'd expect the setup and copying scripts  
for Jetty to mess things up a bit - but new instance creation seems to  
work fine.)

Connection to MySQL works fine - after years of Mckoidb, it's nice to  
be able to run an SQL client and see what's going on - and I managed  
to import a few site XMLs happily, apart from one or two wrinkles to  
do with entity encoding.

It's not 100% plain sailing - there were a few false starts and some  
EL tag whines while I moved things around - but my feeling at this  
stage is that the SnipSnap code base is pretty serviceable. I don't  
know how it *works*, but that's an issue for another day.

I think Paulo deserves the credit for keeping SnipSnap alive - I don't  
know if he's on this list, but I've dropped him a line to see what his  
plans are.

	-- N.

Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.last.fm/music/cassiel
www.reverbnation.com/cassiel
www.linkedin.com/in/cassiel
www.loadbang.net