Embedded server started non-modular use only first --jboss-home for FS paths ---------------------------------------------------------------------------- Key: WFCORE-1675 URL: https://issues.jboss.org/browse/WFCORE-1675 Project: WildFly Core Issue Type: Bug Components: CLI, Domain Management Reporter: Ken Wills Assignee: Ken Wills Priority: Blocker First --jboss-home value passed is always used to FS paths resolution. The issue affects embed-server started using jboss-cli-client.jar. *reproduce* start embed server using eap1, stop it, start another embed server using eap2 {noformat} /home/pkremens/workspace3 ├── eap1 │ └── jboss-eap-7.1 └── eap2 └── jboss-eap-7.1 [pkremens@dhcp-10-40-5-78 client]$ pwd ; java -jar jboss-cli-client.jar /home/pkremens/workspace3/eap1/jboss-eap-7.1/bin/client [disconnected /] embed-server --jboss-home=~/workspace3/eap1/jboss-eap-7.1 [standalone@embedded /] stop-embedded-server [disconnected /] embed-server --jboss-home=~/workspace3/eap2/jboss-eap-7.1 {noformat} *actual* _eap1_ is used {noformat} ... "name" => "jboss.server.config.dir", "path" => "/home/pkremens/workspace3/eap1/jboss-eap-7.1/standalone/configuration", ... {noformat} [Full output|http://pastebin.test.redhat.com/395395] - only jboss.home.dir reflects a new jboss-home *expected (7.0.0 behaviour)* _eap2_ is used {noformat} ... "name" => "jboss.server.config.dir", "path" => "/home/pkremens/workspace3/eap2/jboss-eap-7.1/standalone/configuration", ... {noformat} Setting priority to Blocker since this is a regression against 7.0.0