[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9277: ------------------------------------ At the moment, this is by design. Max's specific use case involves demanding no launches (and thus no polling) so that he can "publish" in an AS7-type method, to another workspace folder. Then, he wants it to commit to git. In order for wtp to automatically publish all the time, the server must be in 'started' mode. Max? Any thoughts? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9277: -------------------------------------------- note, some of the pollers actually do make sense for this one. i.e. http and management ones. But process poller does not since that is dependent on an actual launch to run. Could the pollers be made aware of how they should react? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9277. -------------------------------- Release Notes Text: Externally managed servers will not be launched or polled. The new text reads "Server is externally managed. Assume server is started." An "externally-managed" server has it's state set to 'started' automatically. An "externally-managed" server cannot be stopped or restarted. Resolution: Done Externally managed servers will not be launched or polled. The new text reads "Server is externally managed. Assume server is started." An "externally-managed" server has it's state set to 'started' automatically. An "externally-managed" server cannot be stopped or restarted. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9277: -------------------------------------------- My comment about pollers were to your previous questions - not about the commit. If I before said that deploy only should always be in started mode then I'm stupid - I only remember deploy only mode having the problem of not being able to be started - it just sat there and you had to manually invoke publish. What I wanted or at least want now is that I can start and stop these server adapters so there is a way to start/stop the deployment/interaction. If you don't like the *label* "Assume started" then i'm fine with changing that to something else - that was just a suggestion. But being able to explicitly start/stop the server feels like a much smoother workflow to me than its always publishing automatically - and no, I don't think automatic publishing should be disabled for these to workaround that. With respect to deploy-only server then that would also match great, especially if we finally get a way to start/stop the deploy-only server with custom scripts for user - but thats a separate issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-9277: ------------------------------------- Maybe this is not the right time to jump into discussion, but I couldn't resist ;) What about adding another check box? Server editor could look like: CHECK[1] : Manager Startup/Shutdown (default checked) CHECK[2]: Poll server state (default checked) COMBO[3] : List of available pollers (default enabled) if you uncheck [1], content of [3] refeshes and removes pollers that don't make sense. iyou apply to usecase, when server might run and tooling does not care, but makse you sure that it runs if you uncheck[2] list of pollers gets disabled - with [1] unchecked this is same as deploy-only adapter (but of course for AS7 it will work, deploy-only won't) maybe once you have checked [1] you cannot uncheck [2] because tools needs poller when it starts/stops server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-9277 at 7/7/11 11:46 AM: ------------------------------------------------------------------ Libor, your suggestion makes a lot sense to me and helped me a bit to understand what we are heading towards. I would still like to clear up the basics (please correct): The server in the server view should report ([started] or [stopped]): * deploy only server adapter: adapter state * all other adapters: server state But we still want to start/stop the adapter: * "start" on deploy only adapter: starts the adapter * "start" on all other adapters: starts the adapter & the server unless it's told to not execute launch commands The consequence of always reporting the server state for the server adapters (not deploy only adapter) is that we would loose automatic deployment if the server is down. I guess we should meet and sync up about this. was (Author: adietish): Libor, your suggestion makes a lot sense to me and helped me a bit to understand what we are heading towards. I would still like to clear up the basics (please correct): The server in the server view should report ([started] or [stopped]): * deploy only server adapter: adapter state * all other adapters: server state But we still want to start/stop the adapter: * "start" on deploy only adapter: starts the adapter * "start" on all other adapters: starts the adapter & the server unless it's told to not execute launch commands I guess we should meet and sync up about this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9277: --------------------------------------- Assignee: Rob Stryker (was: Max Rydahl Andersen) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9277. -------------------------------- Resolution: Done Greying out the pollers when server is ignoring launches =] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9277?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-9277: ------------------------------------- verified on JBossAS Tools 2.3.0.v20110825-1600-H670-M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira