Hi Dave, Yes, it's probably a good time to put out a new release of that provider.
Best, Jim On Mon, Aug 15, 2016, 7:22 AM Dave Senn <dave.jon.s...@gmail.com> wrote: > Hi Apache developers > > The current version of Apache.NMS.STOMP is not released. > The latest available version is 1.5.4, see: > http://activemq.apache.org/nms/stomp-downloads.html > Version 1.5.4 is not compatible with any Broker other than Apache MQ, > Apache > Apollo, or maybe Apache Artemis (not tested). This problem was fixed by Jim > Gomes, see: https://issues.apache.org/jira/browse/AMQNET-492 > > Would it be possible to release the current version 1.7.1 of > Apache.NMS.STOMP? > The version 1.7.1 should contain the following fixes: > > https://issues.apache.org/jira/browse/AMQNET-394?jql=project%20%3D%20AMQNET%20AND%20status%20%3D%20Resolved%20AND%20affectedVersion%20in%20(1.5.4%2C%201.5.5%2C%201.5.6%2C%201.6.0%2C%201.6.1%2C%201.6.2%2C%201.6.3%2C%201.6.4%2C%201.6.5%2C%201.7.0%2C%201.7.1%2C%201.7.2)%20AND%20component%20%3D%20Stomp%20ORDER%20BY%20priority%20DESC > * Zombie Consumer is created after failover > * MessageId assumed to be a number > * ResponseCorrelator transport is not stopped when Connection is closed > * TcpTransport.cs - Close() taking 30 seconds > * Add IDisposable interface to IDestination. > * Port the NMS library, Stomp and MQTT providers to Xamarin Android > * Port the ignoreExpiration option from Apache.NMS.ActiveMQ to > Apache.NMS.Stomp > > All this fixes are not currently available to any Apache.NMS.STOMP users. > This list of fixed issues and the fact that the currently released version > of Apache.NMS.STOMP (1.5.4) is not compatible with the latest released > version of Apache.NMS (1.7.1) should be reason enough to > release the latest version of Apache.NMS.STOMP. > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Release-current-version-of-Apache-NMS-STOMP-tp4715483.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >
