You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/08/27 04:09:05 UTC
[jira] Updated: (GERONIMO-477) Deployer should not auto-connect if not asked to
[ http://issues.apache.org/jira/browse/GERONIMO-477?page=all ]
Aaron Mulder updated GERONIMO-477:
----------------------------------
Component: deployment
Fix Version: 1.0-M5
Description:
Before dropping back to offline mode, the new deployer tries to auto-connect to a server running on the local machine. Since this feature was added I have run into a problem where it is connecting to the wrong server. For example, the Geronimo build will just hang during assembly if there is another server running in the background.
There has been talk about splitting the online and offline functions into two tools; if this is done I don't think this will continue to be an issue as the online one could try and connect but the offline one which is used during the build won't.
If we stick with one tool them I think we should add a --offline option that stops the deployer from trying to connect. It seems to me that one tool approach is getting confusing.
was:
Before dropping back to offline mode, the new deployer tries to auto-connect to a server running on the local machine. Since this feature was added I have run into a problem where it is connecting to the wrong server. For example, the Geronimo build will just hang during assembly if there is another server running in the background.
There has been talk about splitting the online and offline functions into two tools; if this is done I don't think this will continue to be an issue as the online one could try and connect but the offline one which is used during the build won't.
If we stick with one tool them I think we should add a --offline option that stops the deployer from trying to connect. It seems to me that one tool approach is getting confusing.
Version: 1.0-M4
Environment:
> Deployer should not auto-connect if not asked to
> ------------------------------------------------
>
> Key: GERONIMO-477
> URL: http://issues.apache.org/jira/browse/GERONIMO-477
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M4
> Reporter: Jeremy Boynes
> Fix For: 1.0-M5
>
> Before dropping back to offline mode, the new deployer tries to auto-connect to a server running on the local machine. Since this feature was added I have run into a problem where it is connecting to the wrong server. For example, the Geronimo build will just hang during assembly if there is another server running in the background.
> There has been talk about splitting the online and offline functions into two tools; if this is done I don't think this will continue to be an issue as the online one could try and connect but the offline one which is used during the build won't.
> If we stick with one tool them I think we should add a --offline option that stops the deployer from trying to connect. It seems to me that one tool approach is getting confusing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira