[jboss-jira] [JBoss JIRA] (WFCORE-1809) JBoss CLI patch command doesn't honor custom configuration location

[Alexey Loubyansky (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13320568#comment-13320568 ] 

Alexey Loubyansky commented on WFCORE-1809:
-------------------------------------------

We could. But before doing anything about it I would like to see a real customer demand first and address that.
This issue was, in fact, inspired by a customer case. The customer was confused and didn't actually realize we didn't patch the configuration. Once that was cleared out, the customer didn't have any requests. So before implementing this feature and taking the responsibility for it, I want to receive an actual customer request.

> 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)