sts-- there is only *one*
> >> testSourceDirectory so you have to jump through hoops with
> >> includes/excludes and extra surefire executions to make it work.
> >>
> >> The best bet is to move the acceptance tests to a separate module.
> >> Then you can use a profile to selectively enable or disable it.
> >
t;>
>> There is some info on the wiki:
>> http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
>>
>> --
>> Wendy
>>
>> ---
That's disappointing to hear. I would imagine separating
integration/acceptance tests is a fairly common
issue.
Altering the layout of the source tree isn't really an option for me (big
corporate environment).
The link you sent had an interesting idea. If I exclude the Acceptance
Tests from the
On Wed, Aug 27, 2008 at 7:33 AM, Bryan Young <[EMAIL PROTECTED]> wrote:
> I would like to build my project skipping my acceptance tests, but still run
> my unit tests. This seems simple enough if I alter the includes/excludes
> for the surefire plugin, but I want to make this decision at the comma
I would like to build my project skipping my acceptance tests, but still run
my unit tests. This seems simple enough if I alter the includes/excludes
for the surefire plugin, but I want to make this decision at the command
line. Essentially what I want is a property like this:
-Dmaven.acceptance.
