maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Gudian <andreas.gud...@gmail.com>
Subject Re: SureFire 2.16 doesn't respect forkCount
Date Wed, 25 Sep 2013 21:40:46 GMT
Ah, ok. I see what happens. Maven-core replaces the stand-alone term
${surefire.forkNumber} during the normal property resolving phase with an
empty String (it does not know any properties with that name in the pom).
Try using:
<surefire.forkNumber>$${
surefire.forkNumber}</surefire.forkNumber>



2013/9/25 Laird Nelson <ljnelson@gmail.com>

> On Wed, Sep 25, 2013 at 2:15 PM, Laird Nelson <ljnelson@gmail.com> wrote:
>
> > Well, here's the innards of my test class itself so you might be able to
> > see if I'm doing something idiotic
> >
>
> Ah, dammit, I AM doing something idiotic.  Or expecting something idiotic
> anyway.
>
> First up, I apologize for the noise.  I think mentally I was (for no good
> reason) expecting to see a new fork for each METHOD.  Duh.
>
> However, I would still expect to see something in the system property,
> yeah?
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message