Echofon does not support this platform or custom build Firefox. (Can’t get OAuth signer.) / Cc['@naan.net/twitterfox-sign;1'] is undefined (Fx version 3.6.9 / ABI x86-gcc3)

investigating further, i first came across a blog entry from today on echofon’s blog, stating:

Today, we released Echofon for Firefox version 1.9.6.6 which removes Basic Auth support. This means, Echofon for Firefox no longer supports custom build Firefox (such as 64bit build on Mac/Windows), FreeBSD, Solaris and the other minor platforms. We’re working on the other solution to support these platforms now. Thank you for your patience. (emphasis added)

looking at the echofon plugin review page at mozilla’s plugin web page, it emerges that echofon managed to turpedo their own plugin on redhat linux as well as on ubuntu linux (and not just the 64bit version, but the 32bit version) — which i guess translate to the other minor platforms. ouch.

update: just found out that the 1.9.6.4 version still works, so this might work as a temporary duct tape until echonfon gets their act together.

what was a bit of a pain was getting the proper classpath constructed so that not only target/classes was picked up but also all the required dependencies. poking a bit around in maven’s plugin documentation i came across the dependency plugin and in particular the dependency:build-classpath mojo, armed with that information i came up with the following rather useful shell script:

#!/bin/bash
top=$(pwd)
cwd=$(pwd)
while  [ "$top" != "/" -a ! -e "$top/pom.xml" ] ; do
    cd ..
    top=$(pwd)
done
cd $cwd

if [ -e "$top/pom.xml" ] ; then
    cd $top

    echo "generating scala classpath based on maven pom.xml"
    mvn dependency:build-classpath -Dmdep.outputFile=.classpath-scala

    echo "starting scala"
    scala -cp target/classes:$(cat .classpath-scala)

else

    echo "cannot find top level pom.xml! must have taken a wrong turn somewhere. sorry."
    exit 1

fi

save under a convenient name, stir, and enjoy: call this script instead of calling scala directly.

• install — just installs the JAR file and the POM file, if the -DcreateChecksum=true flag is provided it will create the SHA1 for the JAR only
• deploy — install JAR and POM and all necessary meta data along with SHA1s

to install a package to a shared repository a deploy is to be preferred over an install as with an install we’ll get missing checksum errors later in life.

so, this works like this (using the lift-ldap package as an example):

$ mvn deploy:deploy-file -DgroupId=net.liftweb -DartifactId=lift-ldap -Dversion=1.0.0 -Dpackaging=jar -Dfile=target/lift-ldap-1.0.0.jar -DcreateChecksum=true  -Durl=scp://eyeteadee.zurich.ibm.com/var/www/eyeteadee.zurich.ibm.com/maven