[jboss-jira] [JBoss JIRA] (WFCORE-3909) jboss-cli script does not delegate -D properties to java process

[Jean-Francois Denise (JIRA)]

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

Jean-Francois Denise commented on WFCORE-3909:
----------------------------------------------

[~eduda], the picture seems a bit more complex. CLI launcher does propagate the system properties (by direct calls to setProperty), but it does that after logging has been initialised.
As you suggest, It should be handled at the script level.
 

> jboss-cli script does not delegate -D properties to java process
> ----------------------------------------------------------------
>
>                 Key: WFCORE-3909
>                 URL: https://issues.jboss.org/browse/WFCORE-3909
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI, Scripts
>    Affects Versions: 5.0.0.Final
>            Reporter: Erich Duda
>            Assignee: Jean-Francois Denise
>
> *Scenario:* I want to change logging configuration of CLI using system properties. My expectation is that I just put the properties on command line as arguments.
> {code}
> ./jboss-cli.sh -Dlogging.configuration=... -Djboss.cli.log.level=TRACE -Djboss.cli.log.level=TRACE
> {code}
> However what I actually have to do is to put the properties into the {{JAVA_OPTS}} env variable.
> {code}
> JAVA_OPTS="-Dlogging.configuration=... -Djboss.cli.log.level=TRACE -Djboss.cli.log.level=TRACE" ./jboss-cli.sh
> {code}
> This is different behavior than I am used to standalone.sh script. IMO it is more natural to put the properties as arguments of the script.



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