openejb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacek Laskowski (JIRA)" <>
Subject [jira] Closed: (OPENEJB-698) usage: deploy ... upon executing openejb undeploy
Date Wed, 12 Dec 2007 17:54:43 GMT


Jacek Laskowski closed OPENEJB-698.

    Resolution: Fixed
      Assignee: David Blevins

It's already fixed in trunk (perhaps Dave took care of it not the issue). Committed revision
603684 - a change for returning when no modules given and after help's printed out.

> usage: deploy ... upon executing openejb undeploy
> -------------------------------------------------
>                 Key: OPENEJB-698
>                 URL:
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 3.0-beta-1
>            Reporter: Jacek Laskowski
>            Assignee: David Blevins
>             Fix For: 3.0-beta-2
> jlaskowski@dev /cygdrive/c/openejb-3.0-beta-1
> $ ./bin/openejb undeploy
> Must specify an module id.
> usage: deploy [options] <file> [<file>...]
> Connects to the server and deploys the application.  Note that full remote
> deployment is not yet supported, deployment can only be done on the same
> machine as the server.  Track OPENEJB-609 for development of full remote
> deployment feature.
> Options:
>  -h,--help               Lists these options and exits.
>  -s,--server-url <url>   Sets the url of the OpenEJB server to which the
>                          app will be deployed.  The value should be the same as the JNDI
>                          URL used to lookup EJBs.  The default is 'ejbd://localhost:4201'.
>  -v,--version            Prints the OpenEJB version and exits.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message