You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/06/06 10:08:00 UTC

[jira] [Work logged] (AMQNET-637) NMS 2.0

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

ASF GitHub Bot logged work on AMQNET-637:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Jun/22 10:07
            Start Date: 06/Jun/22 10:07
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce commented on PR #18:
URL: https://github.com/apache/activemq-nms-openwire/pull/18#issuecomment-1147280973

   +1 from me, with same test coverage as previous. Main thing here is to note this will be first pass of 2.0 support, so its expected there maybe issues raised from end users, and we simply will have to bug fix those.




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

    Worklog Id:     (was: 778566)
    Time Spent: 19h 50m  (was: 19h 40m)

> NMS 2.0
> -------
>
>                 Key: AMQNET-637
>                 URL: https://issues.apache.org/jira/browse/AMQNET-637
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: NMS
>    Affects Versions: 1.8.0
>            Reporter: Michael Andre Pearce
>            Priority: Major
>             Fix For: API-2.0.0
>
>          Time Spent: 19h 50m
>  Remaining Estimate: 0h
>
> NMS API is still at JMS 1.1 api level, this is to update the NMS api to the latest JMS 2.0 api 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)