You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/09/02 13:56:21 UTC

[jira] [Reopened] (ARTEMIS-700) Cope with LogManager during version changes on Posix systems

     [ https://issues.apache.org/jira/browse/ARTEMIS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram reopened ARTEMIS-700:
------------------------------------
      Assignee: Justin Bertram

> 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
>            Assignee: Justin Bertram
>             Fix For: 1.4.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)