Is "build jetty-standlone" needed?

[Bertrand Delacretaz]

Correct me if I'm wrong but I think there is currently no easy way to 
deploy a Jetty + cocoon system by just copying files created by the 
cocoon build.

One way that I found is as follows:

-create build/jetty-standalone directory

-copy lib/endorsed, tools/loader, tools/jetty, cocoon.sh and cocoon.bat 
to this directory (omitting CVS directories)

Then, copying the build/jetty-standalone and build/webapp directories 
elsewhere gives you a standalone Jetty + Cocoon system that can be 
started with cocoon.sh or cocoon.bat (after setting the correct webapp 
path, like ../webapp).

Question:
Does this warrant a new "jetty-standalone" target in the build, or is 
there already another way?
I volunteer to implement the build target it if makes sense.

-Bertrand