Note that if your code depends on static initializers being called on each
invocation, setting forkMode to "once" will break your tests. This is true
whether the tests are running in M2 or Maven 1.1
Ian
It's better to be hated for who you are
than loved for who you are not
Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078
"Jeff Jensen"
<[EMAIL PROTECTED] To: "'Maven Users List'"
<users@maven.apache.org>
nology.com> cc:
Subject: RE: speed up
test execution
03/15/2006 05:27 PM
Please respond to "Maven
Users List"
With m1.1, setting fork to "once" speeds the execution over "always"
because
it forks to one JVM for all tests, vs a new JVM for each test. What is
your
setting? But I do see Maven running tests slower than inside Eclipse as
well.
-----Original Message-----
From: Manlio Malaidini [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 15, 2006 4:22 PM
To: Maven Users List
Subject: Re: speed up test execution
Thanks for your feedback. This is an option, of course. Is there somewhere
any migration guide from maven 1 to maven 2? Or something like that?
MM
On 3/15/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
>
> I don't have a lot of experience with Maven 1 but I know it is quite
> slow compare to Maven 2. Maybe you should consider upgrading if you
> have performance issues.
>
> On 3/15/06, Manlio Malaidini <[EMAIL PROTECTED]> wrote:
> > Hello everybody,
> >
> > maybe this is a kind of newbie question, but I'm really trying to
> > speed
> up
> > test execution without meaningful result, therefore I'd like to get
> > your feedback.
> >
> > Setup: I'm currently using maven 1.1-beta-1 and eclipse 3.1.0
> >
> > I have many tests that while run inside eclipse take 1/3 of
> > execution time compared to maven, sometimes even less. I'm talking
> > about strict
> unit
> > testing, typically without DB or network interactions.
> >
> > I've tried to not forking, but without any meaningful difference.
> > If I suppress printsummary I don't gain anything at all.
> > I was thinking about skipping TEST*.xml file generation but that
> > doesn't seem to be possible: any test file that I execute a new 60
> > KB file is generated with environment info, but I really don't want
> > it. Ideally I'd like to have just a yes/no information for each
> > test, with more report
> only
> > in case of failure.
> >
> > I've tried googling around without any major result. Documentations
> doesn't
> > say a lot about this, either.
> >
> > I'd really appreciate your feedback.
> > MM
> >
> >
>
>
> --
> Alexandre Poitras
> Québec, Canada
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
