Revision [3] is just the tip of the iceberg. There were other before
mostly related to using dynamic ports and proper cleanup that allowed
the forkMode='once'. One of the other components that would greatly
benefit from that is camel-jms.
On the hanging test on Windows, that's obviously an issue that has to be
resolved and has little to do with the improvements I mentioned. My only
Windows system is an Atom based netbook which I rarely use, I cannot
confirm or deny experiencing that. Christian and Willem are usually
pretty fast at resolving Windows issues.
Speaking of CI and jenkins, I don't know of any asf project that takes
that long to test and sucks so many resources. Fwiw, that's one of the
improvements on my agenda for 3.0.
Cheers,
Hadrian
On 01/24/2012 11:03 AM, Babak Vahdat wrote:
Hadrian,
you mentioned a really good point regarding the improvements by camel-cxf
testing that I intended to bring into the discussion for today anyway:
Last night I was looking at my monitor as the full build on Windows (build
216) was running and was really stumped as the test:
org.apache.camel.component.cxf.cxfbean.CxfBeanTest
Was running, running and running again [1] for exactly 365 minutes, that's
more than 6 hours!
At the last Jenkins killed the build process and now I assume because of
that (and maybe some other reasons as well) we're banned from the build on
Windows due to previous failure(s) [2].
I assume your mentioned revisions like [3] by your post.
[1] https://builds.apache.org/job/Camel.trunk.fulltest.windows/216/console
[2] https://builds.apache.org/job/Camel.trunk.fulltest.windows/217/console
[3] http://svn.apache.org/viewvc?view=revision&revision=1151313
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-Add-camel-test-spring-component-tp5281207p5294755.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
