You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/10/13 16:36:00 UTC
[jira] [Work logged] (ARTEMIS-4002) Allow $ARTEMIS_LOGGING_CONF override by respecting pre-existing value in artemis script
[ https://issues.apache.org/jira/browse/ARTEMIS-4002?focusedWorklogId=816698&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-816698 ]
ASF GitHub Bot logged work on ARTEMIS-4002:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Oct/22 16:35
Start Date: 13/Oct/22 16:35
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4223:
URL: https://github.com/apache/activemq-artemis/pull/4223#issuecomment-1277890063
@gtully, there's conflicts on this now. Given that and @gemmellr's previous comment I think that this PR probably just needs to be closed.
Issue Time Tracking
-------------------
Worklog Id: (was: 816698)
Time Spent: 20m (was: 10m)
> 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: 2.27.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)