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

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

                Author: ASF GitHub Bot
            Created on: 28/Jan/26 00:22
            Start Date: 28/Jan/26 00:22
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on PR #6195:
URL: https://github.com/apache/artemis/pull/6195#issuecomment-3808247596

   although.. I guess we are waiting artemis 3.0 to make that switch..
   We were trying to be compatible with the previous versions and we are trying 
to do it in steps.
   
   We could eventually rename those files now but we would need to do it in a 
compatible way.




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

    Worklog Id:     (was: 1002127)
    Time Spent: 0.5h  (was: 20m)

> Rename bindings and journal files
> ---------------------------------
>
>                 Key: ARTEMIS-5859
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5859
>             Project: Artemis
>          Issue Type: Task
>          Components: Broker
>    Affects Versions: 2.50.0
>            Reporter: Gašper Čefarin
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The broker still uses the "old" activemq naming for bindings and journal 
> files, like activemq-data-1.amq and activemq-bindings-1.bindings.
> I'm opening a PR where the files are renamed to artemis-data-n.amq and 
> artemis-bindings-n.bindings.
> There's also a new function added inside cli's upgrade command, which, for 
> now, always executes on upgrade. It renames all files matching the extensions 
> .amq or .bindings.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to