[jboss-jira] [JBoss JIRA] (WFCORE-1615) Make wildfly-init-redhat.sh consistent with wildfly-init-debian.sh (WFCORE-1121)
Jorge Solorzano (JIRA)
issues at jboss.org
Wed Jun 22 14:33:00 EDT 2016
[ https://issues.jboss.org/browse/WFCORE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jorge Solorzano updated WFCORE-1615:
------------------------------------
Description: To make both scripts more consistent in terms of functionality, WFCORE-1121 apply changes to wildfly-init-redhat.sh scripts but not to wildfly-init-debian.sh. This jira is to mimic the change back to wildfly-init-debian.sh (was: This change is related to WFCORE-1121 Use script name for file related to Wildfly to allow multiple instances easily.
To make both scripts more consistent in terms of functionality, WFCORE-1121 apply changes to wildfly-init-redhat.sh scripts but not to wildfly-init-debian.sh. This jira is to mimic the change back to wildfly-init-debian.sh)
> Make wildfly-init-redhat.sh consistent with wildfly-init-debian.sh (WFCORE-1121)
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1615
> URL: https://issues.jboss.org/browse/WFCORE-1615
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Scripts
> Affects Versions: 3.0.0.Alpha2
> Reporter: Jorge Solorzano
> Assignee: Tomaz Cerar
> Priority: Trivial
>
> To make both scripts more consistent in terms of functionality, WFCORE-1121 apply changes to wildfly-init-redhat.sh scripts but not to wildfly-init-debian.sh. This jira is to mimic the change back to wildfly-init-debian.sh
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list