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

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

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

   I tried to keep compatibility with previous versions by adding that script 
to upgrade.java. I don't like that it will always execute, even after all the 
files will be named artemis-something, so I still want to add some additional 
logic.
   In any case - including this before 3.0 is up to you (maintainers) ... If 
you want to include it now and you think it's not compatible, let me know where 
the issues are.




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

    Worklog Id:     (was: 1002180)
    Time Spent: 40m  (was: 0.5h)

> 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: 40m
>  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