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

[Ingo Weiss (JIRA)]

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

Ingo Weiss commented on WFCORE-1809:
------------------------------------

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

> We neither patch nor update configuration files from the patch tool except optional reset during rollback.

Understood. Could we then try and introduce an option where you could specify the configuration(s) to be backed up based on {{$JBOSS_HOME}}?

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