I would be fine making these projects deprecated but I think there was some pushback from users on this in the past. But I am all for deprecating projects that are no longer maintained actively and have alternatives such as AMQP clients.
On Fri, Mar 1, 2019 at 2:13 PM Justin Bertram <jbert...@apache.org> wrote: > As I've been looking at updating the ActiveMQ website I've wondered about > the status of both NMS & CMS. Contributors, commits, and releases for them > appear to have been low historically and have dwindled recently even more. > > As I understand it, one of the goals of updating the website is to be more > up-to-date and clear so that users can make informed decisions on what > software to use. In that vein, should we change the "status" of these > projects? > > To summarize what I found, there are 9 repositories* total for NMS & CMS. > In the last 3 years there has been a total of 26 commits by 3 developers > (with 1 developer doing 23 of those commits). > > These days users have client options across a wide variety of platforms & > languages mainly due to the proliferation of AMQP (and STOMP to a lesser > degree). Also, the "JMS style" interfaces of NMS & CMS have waned in > popularity as application development has moved to a more "reactive" > approach. Does it make sense anymore to maintain our own stable of > interfaces & clients? Should we mark these as retried or deprecated? > > > Justin > > * https://github.com/apache/activemq-cpp > https://github.com/apache/activemq-nms-msmq > https://github.com/apache/activemq-nms-zmq > https://github.com/apache/activemq-nms-ems > https://github.com/apache/activemq-nms-xms > https://github.com/apache/activemq-nms-stomp > https://github.com/apache/activemq-nms-amqp > https://github.com/apache/activemq-nms-openwire > https://github.com/apache/activemq-nms-api >
