Compile single tools

From a Glen Golden Email:

You certainly can maven an individual Sakai module. Set your directory to sakai/chef-tool, and say "maven". That will re-build the artifact of the module. In this case, it's a .war. Other modules create a .jar.
And it's much faster than a full compile.

If you change a shared api, it's a good idea to do a full compile just to be sure.

Artifacts are always created, not in your target directory (although they may pass through there) but in your local maven repository. That is where the deploy finds things. So after a "maven" from your module, a "maven" from the sakai/deploy will re-deploy all the jars and wars to your tomcat.

Tomcat must be stopped before this, and restarted after. Don't try a live deploy. Because we live over many webapps, and we have references to things in one webapp used in another, we do not fully support a live change of parts.