[
https://issues.apache.org/jira/browse/ARTEMIS-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607096#comment-17607096
]
Gary Tully commented on ARTEMIS-4002:
-------------------------------------
does that mean that the only way to configure is to provide the system property
that is logging impl specific? What is nice about ARTEMIS_LOGGING_CONF is that
it points to the file, and the script gets it used, via whatever the required
system property is. That is nice if an env var points to a config map - there
is no need to be aware of the implementation detail
> 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)
