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

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

                Author: ASF GitHub Bot
            Created on: 06/Jul/21 11:19
            Start Date: 06/Jul/21 11:19
    Worklog Time Spent: 10m 
      Work Description: erwindon commented on pull request #3638:
URL: https://github.com/apache/activemq-artemis/pull/3638#issuecomment-874367011


   everyone should be happy with a PR, so agreed
   (PR https://github.com/apache/activemq-artemis/pull/3643 is nice example)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 619118)
    Time Spent: 4h 50m  (was: 4h 40m)

> CLI removes server-side prefixes from a given address
> -----------------------------------------------------
>
>                 Key: ARTEMIS-3369
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3369
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.17.0
>            Reporter: Erwin Dondorp
>            Priority: Major
>          Time Spent: 4h 50m
>  Remaining Estimate: 0h
>
> The Artemis CLI variations {{producer}}, {{consumer}}, {{browse}} and 
> {{transfer}}, all prepare a destination using function {{getDestination}}. 
> However, this function also removes a prefix that it was not looking for. It 
> tests for a topic prefix ({{topic://}}) and then removes any prefix that was 
> present.
> It should explicitly test for the 2 prefixes it cares about ({{topic://}} and 
> {{queue://}}) and then remove only a recognized prefix when it was present.
> PR is present.
>   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to