I don't think it will help.
I think that Marcos' pom.xml doesn't contain the Karaf <dependency/> and
so it downloads and bootstraps for each test method.
Regards
JB
On 06/17/2013 11:24 AM, Christian Schneider wrote:
Do you already use the EagerSingleStagedReactorStrategy ? See
https://ops4j1.jira.com/wiki/display/paxexam/Reactor+Strategies
It does not help for the startup time but reduces the number of starts.
Christian
Am 14.06.2013 15:37 schrieb "Marcos Mendez" <[email protected]
<mailto:[email protected]>>:
Hi,
Maven only checks the version in the build, as after the first
build, that zip is already in my local .m2. The time I'm quoting is
the actual container (start method) startup time (after creating the
exam system and container). That's what I'm trying to minimize. I
did plan to look at the repos that I'm using, to limit them to the
local only - as I know what I will be installing. But was wondering
if there's anything else I can do.
Regards,
Marcos
On Jun 14, 2013, at 12:44 AM, Andreas Pieber wrote:
Do you reference the apache karaf artifact in your pom files? This
is the only problem I can imagine making plain karaf tests sooooo
slow for you. If you dont enter the karaf distribution in your pom
file as a dependency the test framework doesnt copy it into your
.m2 directory and therefore freshly download it for each test.
Kind regards,
Andreas
On Thu, Jun 13, 2013 at 10:36 PM, Marcos Mendez
<[email protected] <mailto:[email protected]>> wrote:
Hi,
I'm trying to improve the startup time for our integration
tests. I'm using the vanilla maven distribution zip, the exam
tooling, and cut down the featuresBoot to config. Is there
anything else I can do to cut down the startup time? It's
taking around 20-30s to start with no additional
configuration. Any ideas?
Regards,
Marcos
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
