I found almost by accident in the release nots for mcollective 2.2.3 : The STOMP adapter will not be maintained past this release series, we now issue deprecation warnigns ... 2012/02/12 Deprecate the stomp connector 19146
And the ticket is: (9 days old, so not from 2012) http://projects.puppetlabs.com/issues/19146 The release notes for the developpement branches are not better, they talk about the same ticket. So it was decided 9 days agos by a single guy to remove the stomp connector from the production branch of mcollective. But when I googled about 'http://projects.puppetlabs.com/issues/19146', I found nothing. No ticket about the rational for that, no warning for users. All the documentation talks about installing this connector. What a strange communication. The connector is not a small feature to change, I must recheck and re test a lot of things, talks to the security peoples about openning new holes in the firewall. What about peoples using a stomp only message broker ? You should have at least changed the documentation before, as the official requirement for Mcollective on (at least) Redhat are wrong : http://docs.puppetlabs.com/mcollective/reference/basic/gettingstarted_redhat.html Requirements We try to keep the requirements on external Gems to a minimum, you only need: • A Stomp server, tested against ActiveMQ • Ruby • Rubygems • Ruby Stomp Client -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
