And message groups and active-blaze - for now
On 25 Sep 2009, at 18:07, Hiram Chirino wrote:
and even activemq-perftest. Seems we have lots of long running / sock
tests that we don't really run during the build.
I don't see the point of leaving these in for now. I think it may be
best to organize 1 separate module of these tests that we can
periodically execute these against any release of ActiveMQ?
On Fri, Sep 25, 2009 at 1:04 PM, Hiram Chirino <[email protected]>
wrote:
And how about activemq-camel-loadtest ??
On Fri, Sep 25, 2009 at 12:49 PM, Dejan Bosanac
<[email protected]> wrote:
and maybe activemq-repository-builder ?
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Fri, Sep 25, 2009 at 6:48 PM, Dejan Bosanac
<[email protected]> wrote:
Just wanted to bring that up ...
+1
And would add
activemq-camel-loadtest
and probably activemq-groups (Rob what do you think of this?)
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Fri, Sep 25, 2009 at 6:43 PM, Hiram Chirino <[email protected]
>wrote:
I noticed that we have some other dormant modules.. I think
these also
should go into the sandbox. What do you guys think? We could
always
bring them back in a subsequent release if some demand pops up.
Or
perhaps spin them off with an independent release cycle.
activemq-soaktest
activemq-systest
activemq-protocol-buffer
activemq-book
activemq-test-atomikos
Regards,
Hiram
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://fusesource.com/
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://fusesource.com/
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://fusesource.com/
Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My Blog: http://rajdavies.blogspot.com/
I'm writing this: http://www.manning.com/snyder/
