Thx Claus, I think that's really good to have separated the spring
stuff as it will allow blueprint users to not depend on spring at all
at testing.
Btw, I mentioned some time ago integration tests for archetypes, so
here's a pointer:
https://github.com/apache/karaf/blob/trunk/archetypes/itest
On Tue, Jan 24, 2012 at 4:36 PM, Hadrian Zbarcea wrote:
> Ok, let me clarify, there are a few points made here. Making camel-test
> standalone w/o spring dependencies is great, we should do that. Having a
> camel-test-spring is ok too and as you mentioned the primary audience for
> that would be S
onsole>
>>> [2] https://builds.apache.org/job/**Camel.trunk.fulltest.windows/**
>>> 217/console<https://builds.apache.org/job/Camel.trunk.fulltest.windows/217/console>
>>> [3]
>>> http://svn.apache.org/viewvc?**view=revision&revision=1151313&
t; 217/console<https://builds.apache.org/job/Camel.trunk.fulltest.windows/217/console>
>> [3]
>> http://svn.apache.org/viewvc?**view=revision&revision=1151313<http://svn.apache.org/viewvc?view=revision&revision=1151313>
>>
>> Babak
>>
>> --
tp://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/
vision=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.
Ok, let me clarify, there are a few points made here. Making camel-test
standalone w/o spring dependencies is great, we should do that. Having a
camel-test-spring is ok too and as you mentioned the primary audience
for that would be Spring *users*. The point I was making is that,
internally, we
On Tue, Jan 24, 2012 at 4:09 PM, Hadrian Zbarcea wrote:
> Actully, imo, a camel-test-spring should only be used for integration and by
> users, not for unit tests.
>
Do you mean Camel unit testing itself? Why should we not eat our own dog food?
camel-test-spring, is for any kind of Camel + Spri
Actully, imo, a camel-test-spring should only be used for integration
and by users, not for unit tests.
Hadrian
On 01/24/2012 06:16 AM, Claus Ibsen wrote:
On Tue, Jan 24, 2012 at 11:59 AM, Christian Müller
wrote:
In generall a good idea. But I doesn't like to lose the possibilities to
use t
On Tue, Jan 24, 2012 at 11:59 AM, Christian Müller
wrote:
> In generall a good idea. But I doesn't like to lose the possibilities to
> use the annotations like @EnpointInject, ...
>
https://issues.apache.org/jira/browse/CAMEL-4934 will allow to use the
Camel @EndpointInject annotations in pure Ja
In generall a good idea. But I doesn't like to lose the possibilities to
use the annotations like @EnpointInject, ...
One of my bigger intentions for Camel 2.10.0 is to speed up the tests (if
it's possible). In the past we was successful to reduce the time our unit
test needs. At present I don't h
Hi
In the recent work by GNodet to add a new camel-test-blueprint, which
I have recently polished. I noticed that the camel-test classes for
CamelTestSupport has dependency on Spring JARs. This is not the
intent, as there is a CamelSpringTestSupport people should use if they
use Spring.
So I wond
12 matches
Mail list logo
