This could be an <j:if> statement away in the maven-test plugin ... I thought about it for a couple of times too ... :-) ... I have some permutation tests which run 30 minutes.
Siegfried Goeschl CTO ================================= IT20one GmbH mail: [EMAIL PROTECTED] phone: +43-1-9900046 fax: +43-1-52 37 888 www.it20one.at On 21 Jan 2003 at 14:51, [EMAIL PROTECTED] wrote: > I posted an email a while ago about that as well.. I would love to be > able to call maven java:jar -ignore test:test etc.... For the same > reasons you have specified. Purists have said that you should ALWAYS > run tests, but when they slow you down too much, they are just > ignored. I think being able to selectively turn them on and off would > be great. > > Eric > > -----Original Message----- > From: Colin Sampaleanu [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 21, 2003 2:31 PM > To: Turbine Maven Users List > Subject: Mechanism to skip tests > > > 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]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
