[ https://jira.jboss.org/browse/JBIDE-7412?page=com.atlassian.jira.plugin.s... ] Rob Stryker resolved JBIDE-7412. -------------------------------- Resolution: Done Took a while of playing with it to figure out how I wanted it to look. Basically, if it's a deploy-only server, the front page only lets you choose a connection profile. If you want to set the deploy folder, you go to the deployment page and set it there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7412?page=com.atlassian.jira.plugin.s... ] Rob Stryker resolved JBIDE-7412. -------------------------------- Resolution: Done All server types have two pages... on the first page is server mode. This affects start / stop / deployment process etc. What mode is the server in. Local mode or RSE mode? The second page is where you set the deploy folder, whether its in the server's default / all / deploy folder, or a custom folder, or what have you. When it's a JBoss server, it can also start and stop remotely. You must set the server home (to find the start script) and which configuration to use when starting. The second page still has options to deploy in the server/{config}/deploy or in a custom folder. But .metadata option is not possible for RSE. A deploy-only server is not necessarily used with JBoss and can be used with other runtime types. Asking it's JBoss home and configuration name doesn't make sense. Also, the second page (deployment page) is where you actually set the deploy folder. For deploy-only servers, the second page has *never* had the options for .metadata, server's deploy folder, or custom. For deploy-only server, this value was *ALWAYS* custom. Basically it makes no sense for a deploy-only server to have .metadata options locally or rse, it makes no sense to have server's deploy folder for local or remote, etc. And it follows that since deploy-only server cannot start or stop the remote server, or suspend its deployment scanner (since it's a dumb server type) that it has no need to know about the remote server home or the configuration. Even if the fields were there, for deploy only server, those values would never be used, since deployment locations are set on page 2. I'm marking this resolved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7412?page=com.atlassian.jira.plugin.s... ] Max Andersen updated JBIDE-7412: -------------------------------- Assignee: Max Andersen (was: Rob Stryker) Fix Version/s: 3.2.0.CR1 (was: 3.2.0.Beta2) Priority: Blocker (was: Major) -- 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-7412?page=com.atlassian.jira.plugin... ] Max Andersen commented on JBIDE-7412: ------------------------------------- yes, remove it; its broken. -- 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-7412?page=com.atlassian.jira.plugin... ] Max Andersen resolved JBIDE-7412. --------------------------------- Labels: new_and_noteworthy (was: ) Resolution: Done This really shouldn't be hard to fix. Committed removal of .as.ssh dir, .as.ssh from pom.xml and feature.xml. If something else outside our build is referring this plugin directly we want to see it fail now and not after the release and have dead code/plugin to maintain on updatesites etc. -- 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-7412?page=com.atlassian.jira.plugin... ] Dominik Pospisil closed JBIDE-7412. ----------------------------------- Verified (jbdevstudio-product-eap-linux-gtk-x86_64-4.0.0.v201101161618R-H65-CR1.jar). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira