-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rake tasks should take arguments #33
Comments
Are you suggesting something like:
|
Partially. See https://github.com/jimweirich/rake/blob/master/doc/rakefile.rdoc#task-arguments-and-the-environment This would also be sufficient:
|
The difference is that rake knows that the task takes an argument, it shows up in |
@atz so long as the argument isn't required, it's fine with me. |
Several of the rake tasks should take arguments, and certainly the underlying
jettywrapper.rb
methods 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".The text was updated successfully, but these errors were encountered: