A solution for (1) could be doing an `mvn package -Dmaven.test.skip=true`. The '-Dmaven.test.skip=true' skips the test phase. For (2), invoking `mvn test` will run the tests, after compiling the classes of course. I'm not sure about (3), but try invoking `mvn antrun:run`.
On 3/23/07, mavenstart <[EMAIL PROTECTED]> wrote:
Thanks Wendy, For example, sometimes I want to do one of the following tasks only (1) build the war file only without doing the JUNIT test (2) just run the JUNIT only to verify the result (I know I can do this in via Eclipse directly) (3) I want to run JMeter test only without going through all the steps "compile-test-package-install", my JMeter will be run through antrun plugin during the" integration-test" phase I also have another question about the "profile", I found that the dependency setup inside the "profile" will be ignored. For example, I set up a profile for running "JMeter test", I really need to specify the dependency of "ant-jmeter.1.0.jar" plugin globally, if I put it inside the "profile", the maven build won't even look for the plugin, then it complains about missing java class. Thanks much for your time, Wendy -- View this message in context: http://www.nabble.com/If-it%27s-possible-to-define-a-goal-to-choose-the-step-to-run-tf3444204s177.html#a9626742 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
