[
https://issues.jboss.org/browse/WFCORE-1809?page=com.atlassian.jira.plugi...
]
Alexey Loubyansky commented on WFCORE-1809:
-------------------------------------------
Hold on. When you say configurations you mean all configuration files
on that configuration directory, correct?
I actually meant custom config directory
locations. But even if you limit it to the files inside the default directory, the user
can add/remove/edit them. We can't even assume that any XML file in there is a valid
server configuration file.
Correct. The server knows the configuration location through
jboss.server.config.dir. It would be up to the patching mechanism to look for the
remaining .xml files and patch them as needed.
We neither patch nor update
configuration files from the patch tool except optional reset during rollback.
JBoss CLI patch command doesn't honor custom configuration
location
-------------------------------------------------------------------
Key: WFCORE-1809
URL:
https://issues.jboss.org/browse/WFCORE-1809
Project: WildFly Core
Issue Type: Bug
Components: Patching
Affects Versions: 3.0.0.Alpha8
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Suppose we are using custom standalone directory(example: standalone_dev) and if we try
to rollback applied CP patch, with "--rest-configuration=true" option, it always
restore configuration files from default location(JBOSS_HOME/standalone) not from the
"standalone_dev" directory. I can see same result when I try to rollback patch
through management console and through JBoss CLI in connected mode.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)