Comments inline. [EMAIL PROTECTED] wrote on 22/01/2003 06:51:08 AM:
> 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. > -----Original Message----- > From: Colin Sampaleanu [mailto:[EMAIL PROTECTED]] [snip] > 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 'You know it will not affect test' - Famous last words IMHO. > Does anybody agree or have comments? If you're going to build a jar, my take is it should be a functional one, otherwise what's the point? -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
