Well, saying that SMX is dead is absurd. SMX is a brand, more than a project with code ownership. It combines the Camel + CXF + ActiveMQ components running on top of Karaf, so that folks can download the stack and install it easily in one go.
Saying that SMX is dead is equivalent to saying that the upstream projects are dead, which is very very far away from the truth. A different thing would have been to state that SMX hadn't seen a refresh / release in some while. That could've been true back then, but is fortunately no longer the case – as you pointed out already both community and release activity have risen considerably. I'll stay away from conjecturing about the true intentions behind such "shattered glass" and "sensationalist" blog posts. Open Source is all about openness and honesty, and certain types of attitudes benefit nobody. For example, throwing FUD at peer Open Source projects is hardly exemplary. Regards, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Wed, Jul 30, 2014 at 3:55 PM, maggie <[email protected]> wrote: > I know similar questions have been asked before but either questions did > not > cover my concerns or the responses were not clear enough. Let me know if > this should be posted in some other forum. I did not post in Red Hat forum > intentionally though. Here is the question: > > I am in process of upgrading to latest SM. We earlier went with the > Fusesource version of SM as we liked the support behind it even though we > never required it. Now with RH in the picture, upgrade is not that > straightforward. We now have to choose between Fabric 8 vs SM 5 vs Jboss > Fuse. > > Our requirement is: Distributed KARAF containers which can talk Camel, > Spring DM, CXF and have support for ActiveMQ. > > * SM fits the bill perfectly but then I am unable to add fabric to the > latest SM version (5.1.0.). I am not sure If I am missing anything by not > being able to add Fabric > * Fabric 8 to me seems overkill as we are not planning to provision using > Hawtio. We are also not planning to deploy other than KARAF. Cloud support > is a future thing for at this point for us. We want to base our application > on OSGI+Spring support. Additionally vanilla Fabric 8 does not work; you > have to configure Fabric to behave like SM (Camel+ActiveMQ+CXF). On top of > everything the production release of Fabric 8 is not out yet > * Jboss Fuse comes with subscription fee. It is very similar to deploying > on > SM. I am not sure whether Fabric features give us any more value than what > cellar can give on SM given that we are not planning to use Hawtio > > To me looks like sticking to SM + Cellar is way forward. Also I read some > blogs from guys who worked on SM earlier saying that SM is dead. I find > completely opposite. I find quite a few recent releases of SM. I have sense > that some people are intentionally trying to kill SM brand but I am not > sure. > > Look forward to what others have to say about it. > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Servicemix-5-and-cellar-or-Jboss-Fuse-and-Fabric-tp5721456.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
