[jboss-jira] [JBoss JIRA] (WFLY-10242) Unify secmgr JAVA_OPTS behaviour in WF scripts

[Marek Kopecký (JIRA)]

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

Marek Kopecký commented on WFLY-10242:
--------------------------------------

[~jdenise] (cc: [~eduda], [~mnovak]): I find out, that cli script doesn't support secmgr option. Does it make sence to add this parameter to CLI script? CLI allows to start embedded server, and standalone.sh (non-embedded server) script has the secmgr option. Does it make sence to add secmgr parameter to the jdr script too? JDR tool uses embedded cli server too in some cases.

> Unify secmgr JAVA_OPTS behaviour in WF scripts
> ----------------------------------------------
>
>                 Key: WFLY-10242
>                 URL: https://issues.jboss.org/browse/WFLY-10242
>             Project: WildFly
>          Issue Type: Bug
>          Components: Scripts
>            Reporter: Marek Kopecký
>            Assignee: Kabir Khan
>
> Unify secmgr JAVA_OPTS behaviour in WF scripts.
> standalone&&domain&&appclient scripts doesn't allow to use secmgr by JAVA_OPTS definition. wsconsume&&wsprovide scripts allow that (see [this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/resources/content/bin/wsconsume.sh#L83] and [this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/resources/content/bin/wsprovide.sh#L83])
> All scripts should be unified.
> cc: [~asoldano], [~jamezp], [~jbliznak], [~msvehla]



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)