Several of the rake tasks should take arguments, and certainly the underlying jettywrapper.rb methods should. For rake, at least:
rake jetty:download
rake jetty:clean
rake jetty:unzip
jettywrapper.rb's download() method already takes a url argument, but rake doesn't expose it.
In general, you should be able to target a jetty version directly from the command line, without setting global ZIP_URL or previous magic call to jettywrapper.instance.url= or passing arguments to stop(). Side note: I don't get the convenience of "configure via stop() call".
Several of the rake tasks should take arguments, and certainly the underlying
jettywrapper.rbmethods should. For rake, at least:jettywrapper.rb's download() method already takes a url argument, but rake doesn't expose it.In general, you should be able to target a jetty version directly from the command line, without setting global ZIP_URL or previous magic call to
jettywrapper.instance.url=or passing arguments to stop(). Side note: I don't get the convenience of "configure via stop() call".