On Sun, Mar 23, 2008 at 10:58 AM, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 23, 2008 at 4:55 AM, Raymond Feng <[EMAIL PROTECTED]> wrote: > > > It's also safe to ignore this test failure. You can use mvn clean > install -fn to ignore test failures. > > Hi, > > That's interesting and although it's completely off-topic too I > couldn't resist asking why the -fn option is better than disabling the > tests at all with -Dmaven.test.skip=true? > > Jacek > > Probably depends what you want, with -fn the tests still run with - Dmaven.test.skip=true they don't. Not running the tests makes the build much faster but without running the tests you don't know what problems there might be with the jars that get built. A key thing is that with -fn a test failure in one module does not stop the build of other modules, but, the jar for the module with the test failure does not get built so if you want to ignore a test failure but still rebuild a module then you need to use - Dmaven.test.skip=true. On the other hand for things like the itest modules you just want to see the tests results so it doesn't make much sense to use -Dmaven.test.skip=true but -fn can be useful to see how good or bad the state of the code is. ...ant
