[
https://issues.apache.org/jira/browse/ARTEMIS-4020?focusedWorklogId=822192&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-822192
]
ASF GitHub Bot logged work on ARTEMIS-4020:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Nov/22 05:28
Start Date: 01/Nov/22 05:28
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4246:
URL: https://github.com/apache/activemq-artemis/pull/4246#discussion_r1010083439
##########
docs/user-manual/en/versions.md:
##########
@@ -8,6 +8,22 @@ This chapter provides the following information for each
release:
- **Note:** Follow the general upgrade procedure outlined in the [Upgrading
the Broker](upgrading.md)
chapter in addition to any version-specific upgrade instructions outlined
here.
+
+## Upgrading tool
+
+Since version 2.27.0, it is possible to uptadate all the paths of an instance
toward a newer version.
+
+To upgrade to a new version, simply do the following code:
+
+```shell
+cd $NEW_ARTEMIS_DOWNLOAD/bin/
+./artemis upgrade PATH_TO_UPGRADING INSTANCE
+```
+
+artemis, artemis.profile will be updated to the new version.
+
+(Notice: to avoid removing eventual user's customizations of the scripts, we
don't automatically bring new additions to the script. Please check your
artemis and artemis.profile accordingly after the upgrade)
Review Comment:
I think this documentation would make sense in `upgrading.md` as that's
where the general upgrade instructions are. I also think it would be good to
explain why the script should be used instead of the normal manual process of
just changing the `ARTEMIS_HOME` location in `artemis.profile`.
Issue Time Tracking
-------------------
Worklog Id: (was: 822192)
Time Spent: 11h 10m (was: 11h)
> switch to using SLF4J for logging API and use Log4j 2 for broker distribution
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-4020
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4020
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: 2.27.0
>
> Time Spent: 11h 10m
> Remaining Estimate: 0h
>
> Switch to using [SLF4J|https://www.slf4j.org/] as the logging API for the
> code base, with end-uses supplying and configuring an SLF4J-supporting
> logging implementation of their choice based on their needs.
> For the client, applications will need to supply an SLF4J binding to a
> logging implementation of their choice to enable logging. An example of doing
> so using [Log4J 2|https://logging.apache.org/log4j/2.x/manual/index.html] is
> given in (/will be, once the release is out) the [client logging
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/logging.html#logging-in-a-client-application].
> For the broker, the assembly distribution will include [Log4J
> 2|https://logging.apache.org/log4j/2.x/manual/index.html] as its logging
> implentation, with the "artemis create" CLI command used to create broker
> instances now creating a log4j2.properties configuration within the
> <broker-instance>/etc/ directory to configure Log4J. Details for upgrading an
> existing broker-instance is given in (/will be, once the release is out) the
> [version upgrade
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/versions.html].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
