[
https://issues.apache.org/jira/browse/AMQ-8322?focusedWorklogId=767152&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767152
]
ASF GitHub Bot logged work on AMQ-8322:
---------------------------------------
Author: ASF GitHub Bot
Created on: 06/May/22 11:52
Start Date: 06/May/22 11:52
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #729:
URL: https://github.com/apache/activemq/pull/729#issuecomment-1119535536
> Local MacBook Pro (total 32.535s):
> Apache Jenkins CI (total 43.921s):
>
I'm taking it from the comments here and
https://github.com/apache/activemq/pull/729#discussion_r866242620) that 32-44
seconds isnt seen as a that long of a time for this, so thats going to be the
key mismatch in our views. I think thats glacial for testing the stuff actually
being added here, which is almost entirely fluffy wrapping to expose existing
functionality with new API. I wouldnt really want to use 30sec even supposing
if it included all the actual-new-functionality / behavioural stuff that hasnt
yet been implemented.
Issue Time Tracking
-------------------
Worklog Id: (was: 767152)
Time Spent: 14h 20m (was: 14h 10m)
> Implement JMS 2.0 Connection createContext methods
> --------------------------------------------------
>
> Key: AMQ-8322
> URL: https://issues.apache.org/jira/browse/AMQ-8322
> Project: ActiveMQ
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: #jms2
> Fix For: 5.18.0
>
> Time Spent: 14h 20m
> Remaining Estimate: 0h
>
> Add support for JMSContext, JMSProducer and JMSConsumer for working with
> queues
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
