Mechanism to skip tests

[Colin Sampaleanu]

Is there an easy mechanism which I have missed to allow tests to be skipped when performing a target (such as java:jar) which has a dependency on test:test? I've looked at the source for the test and java plugins and can't see anything.

Generally you do want to run tests when building a jar (or some artifact farther down the dependency chain). But it is also a pretty common occurrence that you want to do that target without executing tests, e.g. when you have just changed a property file, etc., and you know it will not affect tests. I realize that 'maven.test.failure.ignore' is available, but that just skips failing if the tests don't run, I am looking for something which allows skipping the running of tests.

Generally, I think you should be able to set whether tests are compiled by default, and allow that value to be toggled easily at runtime, and then a similar mechanism to set whether tests are executed by default, and allow that value to be toggled easily at runtime. This should also work for the reactor.

Does anybody agree or have comments?

Is there a mechanism by which I can dynamically remove dependencies? E.g. one way I can see to handle the above (assuming something isn't added to maven itself) is to have a target in my maven.xml which based on a property, plays with the dependencies dynamically to remove test:test.






--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>