[
https://issues.apache.org/jira/browse/ARTEMIS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437139#comment-15437139
]
ASF GitHub Bot commented on ARTEMIS-700:
----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/735
ARTEMIS-700 Improving how the log manager is found on Posix systems
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis log
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/735.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 #735
----
commit 81262b83b8a15c713841c745e78df24268efcfce
Author: Clebert Suconic <[email protected]>
Date: 2016-08-25T15:24:52Z
ARTEMIS-700 Improving how the log manager is found on Posix systems
----
> Cope with LogManager during version changes on Posix systems
> ------------------------------------------------------------
>
> Key: ARTEMIS-700
> URL: https://issues.apache.org/jira/browse/ARTEMIS-700
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: clebert suconic
> Fix For: 1.5.0
>
>
> Users should be able to upgrade the version of an Artemis_instance by just
> poiting the new home, however if the version of the logger changed that would
> fail. (The user would have to change the script manually).
> I propose the script finds the version instead of the create.
> I am not sure how to do this in windows, this task is just about Posix
> systems for now.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
