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 2018/02/09 16:31:00 UTC
[jira] [Commented] (ARTEMIS-1676) Allow users to override JAVA_ARGS
via environment variables
[ https://issues.apache.org/jira/browse/ARTEMIS-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358620#comment-16358620 ]
ASF GitHub Bot commented on ARTEMIS-1676:
-----------------------------------------
GitHub user mtaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/1862
ARTEMIS-1676 Support overriding of JAVA_ARGS via env variable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-1676
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1862.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1862
----
commit 62d904f47979afae105981144053f30430ecd310
Author: Martyn Taylor <mt...@...>
Date: 2018-02-09T16:29:44Z
ARTEMIS-1676 Support overriding of JAVA_ARGS via env variable
----
> Allow users to override JAVA_ARGS via environment variables
> -----------------------------------------------------------
>
> Key: ARTEMIS-1676
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1676
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Martyn Taylor
> Priority: Major
>
> We currently require users to update the artemis.profile file to change JAVA_ARGS options. However, it's often useful to be able to override certain properties via environment variables. Typical example is when running in a cloud environment, where customisation is often injected via environment variables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)