geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1218) deploy command cannot be run when server is stopped as help indicates
Date Tue, 22 Nov 2005 16:19:42 GMT
    [ ] 

Aaron Mulder commented on GERONIMO-1218:

I think at this point it's a documentation problem.  We've backed off allowing much while
the server is not running.  I'm open to reconsidering if people think this is valuable --
I think the main difference for deploy is that we have to be able to alter the runtime persistent
configuration list, and for redeploy we have to be able to do that plus undeploy.

Note that you can achieve a similar thing by copying your WAR into the hot deploy directory.
 The difference is that it won't actually be deployed until the server is running, so we can
be sure that the server environment is set up properly before starting the deploy process.

> deploy command cannot be run when server is stopped as help indicates
> ---------------------------------------------------------------------
>          Key: GERONIMO-1218
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0-M5
>  Environment: Windows 2000
>     Reporter: Nell Gawor

> I'm not 100% sure if this is a documentation problem or a deployment problem, but I'm
pretty sure its just a documentation problem.  When running
> java -jar deployer.jar help deploy
> The help says:
> "If the server is not currently running, the module will be
> marked to start next time the server is started."
> Trying to actually run
> java -jar deployer.jar deploy hello.war
> when the server is not started starts the offline deployer and complains
> 09:50:56,736 INFO  [SecurityServiceImpl] JACC factory registered
>     Error: This command cannot be run unless connecting to a running
>     server.  Specify --url if server is not running on the default port
>     on localhost.
> Using distribute instead works as expected.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message