Sakai Plugin does not support more than tomcat 5.5

Unassigning this issue as I am unlikely to get time to work on it, and leaving it assigned to me gives the wrong impression.

Committed and tested, no need for this to go into 2.5.x

This is now possible,

The Maven plugin consults properties as classpatch resources for the mappings of the standard locations to physical locations on disk. The name of the properties file is based on the maven environment variable sakai.app.server, there is a default setup for tomcat5 that is used if no configuration is found.

At the moment the deploy.tomcat5.properties uses the following mappings (this is the default)
shared/lib=shared/lib/
server/lib=server/lib/
components=components/
common/lib=common/lib/
webapps=webapps/

and the deploy.tomcat6.properties is
shared/lib=lib/
server/lib=lib/
components=components/
common/lib=lib/
webapps=webapps/

to deploy to tomcat 5 there is no change as this is the default deployment profile. To deploy to tomcat6 you can do the following.

mvn clean install -Dsakai.app.server=tomcat6 -Dmaven.tomcat.home=/Users/ieb/Caret/tomcat6

NB: This only gives us control over the deployment layout, this does not necessarily make tomcat6 work for Sakai.