-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR1
-
None
-
Regression
-
-
-
-
-
-
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
/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
actual
eap1 is used
...
"name" => "jboss.server.config.dir",
"path" => "/home/pkremens/workspace3/eap1/jboss-eap-7.1/standalone/configuration",
...
Full output - only jboss.home.dir reflects a new jboss-home
expected (7.0.0 behaviour)
eap2 is used
...
"name" => "jboss.server.config.dir",
"path" => "/home/pkremens/workspace3/eap2/jboss-eap-7.1/standalone/configuration",
...
Setting priority to Blocker since this is a regression against 7.0.0
- is cloned by
-
-
- Closed
-
- is incorporated by
-
JBEAP-5310 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha4
-
- Verified
-
- relates to
-
-
- Closed
-
