Is it a size of the jar problem? Or is it I just need 1 jar dependency type problem? Or is I can't tell which one I should pick problem?
Regards, Hiram On Tue, Sep 29, 2009 at 4:01 PM, Bruce Snyder <[email protected]> wrote: > In the past, folks have asked me about an ActiveMQ client jar file. > Something that's lighter weight and immediately identifiable as the > artifact to be used from the client side instead of poking around > trying to figure out which jars to use. Today, someone asked me about > this very thing again, so I'd like to discuss the idea. IMO, if it > helps users, then it's worth doing. > > Assuming that we agree to create such a jar file, I see two ways to do it: > > 1) Manually hack together an activemq-client.jar using a Maven > assembly. I've done this in the past on other projects and it's > usually terribly brittle and error-prone. > > 2) Create a new module named activemq-client and begin moving classes > out of activemq-core into the new module. This would mean that the > activemq-core module would have a dependency on the activemq-client, > but that's minor. In fact, improved modularization will only improve > the codebase. If you've ever looked at the ActivMQ codebase in > Structure101 you know badly tangled it is. > > Thoughts? > > Bruce > -- > perl -e 'print > unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" > );' > > ActiveMQ in Action: http://bit.ly/2je6cQ > Blog: http://bruceblog.org/ > Twitter: http://twitter.com/brucesnyder > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://fusesource.com/
