[
https://issues.apache.org/jira/browse/ARTEMIS-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096808#comment-15096808
]
ASF subversion and git services commented on ARTEMIS-336:
---------------------------------------------------------
Commit 500704a7ccfe76b56feb738ee7918eafbab96caf in activemq-artemis's branch
refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=500704a ]
ARTEMIS-336 Windows script updates
> Don't hard-code instance path
> -----------------------------
>
> Key: ARTEMIS-336
> URL: https://issues.apache.org/jira/browse/ARTEMIS-336
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Fix For: 1.3.0
>
>
> This was reported via the developer mailing list:
> http://activemq.2283324.n4.nabble.com/Artemis-incomplete-use-of-ARTEMIS-INSTANCE-td4705750.html
> Artemis uses only partially the ARTEMIS_INSTANCE environment variable and its
> associated artemis.instance Java property.
> When creating a new instance with "artemis create mybroker":
> (1) etc/artemis.profile contains the expanded ARTEMIS_INSTANCE path
> hard-coded in the JAVA_ARGS line, it should use $ARTEMIS_INSTANCE instead
> (2) etc/bootstrap.xml contains the expanded ARTEMIS_INSTANCE path hard-coded
> in the server's configuration attribute, it should use ${artemis.instance}
> instead
> This way, it would be easier to relocate an Artemis instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
