Release plugin depends on mvn being in the path of the shell that started the current build

It's impossible to run a project release from an environment that uses maven without putting it in the path environment variable. This causes problems with build servers like Hudson, where you want to be able to configure on a project-by-project basis the version of Maven being used. The only alternative is to choose a version of Maven to put into the shell environment PATH used to start the appserver.