A couple of other questions about differences from m1.
In m2 it seems that the test message output is being buffered and not
displayed until all tests have been run. Is there a way to change that?
In m1 I could tell maven to only run tests matching a certain criteria
with something like "maven -Dtestmatch=Object* test:match". Is this
possible right now, and if not is it planned for the future? If so, when?
Thanks again,
Rich
Richard Wallace wrote:
Hey everyone,
I'm trying to move a maven 1 project to maven 2. All the dependencies
look like they're working fine now, and I'm able to build and run the
tests.
When running the tests, there is a quite a bit of output going to
stdout, such as Hibernate query statements. In maven 1 I used the
properties
||maven.junit.fork=true
maven.junit.dir=${maven.build.dir}/test
to do a couple of things. Forking the process would make the stdout
go into the .txt reports. Setting the directory it's run in would
make it so any log files created during the test runs, such as the
p6spy and the log4j logs, would be put in the test directory rather
than the root project directory. To make this work I also had to have
a preGoal in my maven.xml file for test:prepare-filesystem to create
that test directory before the tests were run.
I'm wondering how I can accomplish the same thing, or at least
something similar, with m2. Any ideas?
Thanks,
Rich
---------------------------------------------------------------------
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]
