[ 
https://issues.apache.org/jira/browse/ARTEMIS-4081?focusedWorklogId=824263&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-824263
 ]

ASF GitHub Bot logged work on ARTEMIS-4081:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Nov/22 15:59
            Start Date: 08/Nov/22 15:59
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on code in PR #4282:
URL: https://github.com/apache/activemq-artemis/pull/4282#discussion_r1016825163


##########
artemis-cli/src/main/java/org/apache/activemq/artemis/cli/commands/Upgrade.java:
##########
@@ -31,10 +31,20 @@
 import java.util.stream.Stream;
 
 import io.airlift.airline.Command;
+import org.apache.activemq.artemis.util.JVMArgumentParser;
 
 @Command(name = "upgrade", description = "Update an artemis instance to the 
current artemis.home, keeping all the data and broker.xml. Warning: backup your 
instance before using this command and compare the files.")
 public class Upgrade extends InstallAbstract {
 
+   // these are the JVM argumnents we must keep between upgrades:w

Review Comment:
   ouch.. vim





Issue Time Tracking
-------------------

    Worklog Id:     (was: 824263)
    Time Spent: 1h 50m  (was: 1h 40m)

> Upgrade command
> ---------------
>
>                 Key: ARTEMIS-4081
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4081
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.27.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> We should add a command to upgrade an instance from an older broker.
> ./artemis upgrade <old-instance> should update the required scripts and files 
> to reflect a new broker home.
> The touched files should be backed up for easy recovering in case of failure 
> and also for the user to compare eventual configuration they might have done 
> on scripts.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to