That's the question. How accommodating should a community be with all the usage scenarios of its artifacts? The only solution I see is to engage the smack guys and see what their interest is, what help they could use and how we could cooperate. It's apache licensed, so personally I'm willing to help.
Hadrian On Oct 13, 2010, at 4:33 PM, Donald Whytock wrote: > Would they be the ones to supply osgi-ready bundles? Or could Camel > be bundled with an osgi'd version of the smack jars? > > Don > > On Wed, Oct 13, 2010 at 1:23 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: >> You could, but we cannot include it with a dependency on a snapshot. >> I am working on figuring out the best way to publish 3rd party releases in >> the central repo, so that we avoid such issues. >> It looks I also need to get in touch with the smack guys and see if they >> have any plans for new releases. >> >> Thanks, >> Hadrian >> >> >> On Oct 13, 2010, at 1:15 PM, preben wrote: >> >>> >>> I started extending the existing xmpp component to support xmpp pubsub using >>> a subproject of Smack as supposed by >>> http://camel.465427.n5.nabble.com/XMPP-pubsub-td3199018.html#a3199018. >>> >>> The existing Smack trunk includes pubsub support, but it hasn't been >>> released. >>> >>> Should I attach a patch ? >>> >>> Thanks >>> Preben >>> >>> >>> -- >>> View this message in context: >>> http://camel.465427.n5.nabble.com/XMPP-pubsub-tp3074364p3210891.html >>> Sent from the Camel - Users mailing list archive at Nabble.com. >> >>
