If maven.test.skip is set (or if there are no unit tests), there should be no need to execute test:test-resources.
This allows putting preGoals and postGoals against test:test-resources which may be very time-consuming (such as database loads), and these other goals would not be executed if the tests are not run.
Description
If maven.test.skip is set (or if there are no unit tests), there should be no need to execute test:test-resources.
This allows putting preGoals and postGoals against test:test-resources which may be very time-consuming (such as database loads), and these other goals would not be executed if the tests are not run.
Todd Huss added a comment - 24/Feb/05 05:56 PM I believe I'm having the same problem. If I define a pregoal for test:test and then run maven as:
maven -Dmaven.test.skip=true
it still executes my pregoal.
Current solution introduces MPTEST-66. Other plugin expect test plugin to attain java:compile.
The prereqs in test:* goals should be splited to allways invoque java:compile, and skip test:compile is skip=true
nicolas de loof added a comment - 21/Jul/06 05:34 AM Current solution introduces MPTEST-66. Other plugin expect test plugin to attain java:compile.
The prereqs in test:* goals should be splited to allways invoque java:compile, and skip test:compile is skip=true
Improvement
Closed
Minor
Do not execute test:test-resources unless tests will be run
I believe I'm having the same problem. If I define a pregoal for test:test and then run maven as:
maven -Dmaven.test.skip=true
it still executes my pregoal.