My guess is that while -fn tells maven never to fail, it doesn't tell it at what point in the lifecycle to finish. It's likely that the test goal failed, maven stopped (before executing the install goal) and reported a successful build. In the second case you're removing the test goal from the maven lifecycle, so maven gets to the install goal.
On Tue, Aug 4, 2009 at 2:14 PM, Naftoli Gugenheim<naftoli...@gmail.com> wrote: > > Thanks. Not sure why only the latter did an install. > > ------------------------------------- > Indrajit Raychaudhuri<indraj...@gmail.com> wrote: > > > Telling maven to never fail: > mvn -fn (NEVER fail the build, regardless of project result) > > Telling maven to skip test: (quite different from never failing) > mvn -Dmaven.test.skip=true > > /irc > > On 05/08/09 2:27 AM, Naftoli Gugenheim wrote: >> >> How do you tell maven to install even if tests fail? >> >> > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
