On 27/05/2009, at 3:18 PM, Brett Porter wrote:
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow regular expressions in
addition
to the ant syntax.
Cool, but that's another release in the chain, right?
Then we can do (?!.*/src/.*).*/target/.*
Ew
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow regular expressions in
addition
to the ant syntax.
Cool, but that's another release in the chain, right?
Then we can do (?!.*/src/.*).*/target/.*
Ew :)
What if the build directory isn't target? (unl
I really like the idea of breaking up unit, integration, and functional tests.
This is how I would prefer to break up my tests. I had to use TestNG groups to
do this effectively in the current scheme of things.
Thanks for the link!
Jason
-Original Message-
From: Stephen Connolly [mai
2009/5/26 Jason Chaffee
> Yep, I concur with you a 100%. I think the solutions for this until now
> (FailSafe), were highly undesirable and caused many other issues.
>
> It might be something the Maven folks might want to think about in the
> future, adding support for integration testing in an
Yep, I concur with you a 100%. I think the solutions for this until now
(FailSafe), were highly undesirable and caused many other issues.
It might be something the Maven folks might want to think about in the future,
adding support for integration testing in an more appropriate way (adding the
We're fixing the directoryscanner to allow regular expressions in addition
to the ant syntax. Then we can do (?!.*/src/.*).*/target/.*
On Mon, May 25, 2009 at 6:58 PM, Brett Porter wrote:
> How about an option true
> that uses the list of build directories from all projects in the reactor an
>