The general idea is you wouldn't want to produce the final jar if the unit tests are failing. Wouldn't failing unit tests indicate the code is not working properly? In reality you can proceed to build the site with failing tests showing up in the report. The default jar target will not complete though with failing unit tests. It's been brought up previously and I'm -1 on allowing the user to change this behavior, but would be +0 to adding a separate target ( ant maven:jar-not-tested ) to build the untested jar without depending on the unit test target.
================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com > -----Original Message----- > From: John Keyes [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, June 12, 2002 9:42 AM > To: [EMAIL PROTECTED] > Subject: Calling <fail/> if <junit/> fails > > > Hi, > > Why is <fail/> called if the <junit/> task fails? > It think it should continue as normal and the > JUnit report page will contain the failure details or > at least have it configurable whether <fail/> is > called or not. > > -John K > > > > -- > 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]>
