[jbosstools-issues] [JBoss JIRA] (JBIDE-18254) Change in remote server's config dir is not reflected in the launch command

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-18254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina updated JBIDE-18254:
----------------------------------
    Steps to Reproduce: 
1. Create a remote EAP 6 / AS 7 / WildFly 8 server
2. Open server editor, change Remote Server Base Directory to something other than the default "standalone"
3. Start the server / check the launch command used in launch config
 - you will see that the new dir is used to set up logging, but not for the standalone.xml config - that still only has --server-config=standalone.xml

  was:
1. Create a remote EAP 6 / AS 7 / WildFly 8 server
2. Open server editor, change Remote Server Base Directory to something other than the default "standalone"
3. Start the server / check the launch command used in launch config
 - you will see that the new dir is used to set up logging, but not for the standalone.xml config - that still only has --config=standalone.xml



> Change in remote server's config dir is not reflected in the launch command
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-18254
>                 URL: https://issues.jboss.org/browse/JBIDE-18254
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.CR1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.CR2
>
>
> When you create a remote server and then change the Remote Server Base Directory from standalone to something else, this change is not reflected in the config= setting in the launch command.
> This may apply to local servers as well.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)