[jira] [Comment Edited] (ARTEMIS-4002) Allow $ARTEMIS_LOGGING_CONF override by respecting pre-existing value in artemis script

["Robbie Gemmell (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607041#comment-17607041 ] 

Robbie Gemmell edited comment on ARTEMIS-4002 at 9/20/22 9:29 AM:
------------------------------------------------------------------

The ARTEMIS_LOGGING_CONF variable has been removed entirely on the new-logging branch already.


was (Author: gemmellr):
The ARTEMIS_LOGGING_CONF variable has been removed entirely on logging branch already.

> Allow $ARTEMIS_LOGGING_CONF override by respecting pre-existing value in artemis script
> ---------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4002
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4002
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 2.25.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Trivial
>             Fix For: 3.0.0
>
>
> We set the logging system property using an env var, however we don't allow that env var to be provided, it is currently overwritten
> When the env can be easily modified, it would be great to be able to easily provide an alternative logging file via setting the $ARTEMIS_LOGGING_CONF variable.
> We just have to set it only when it is empty!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)