I'm 100% with Brill on this one, although one strong caveat is to make sure your Eclipse environment (dependencies, etc.) match the environment in which JUnit executes through maven. Once you sync environment settings (*ahem* "maven eclipse"), life is really pretty easy. Eclipse gives you a pretty read-out for what failed, and where...and you can run in debug mode on a case-by-case basis.
-j On Wed, 2004-07-07 at 15:25, Brill Pappin wrote: > When I find a test failing during a build, I simply go back to eclipse > and run it ,manually on its own. > You can also look at the reports in the target dir for more information. > > -Brill Pappin > > David Erickson wrote: > > >I just need step by step for java code.. specifically my unit tests as they > >are being executed.. can you give me more info on how to do this? :) Thanks, > >-David > >----- Original Message ----- > >From: "Dion Gillard" <[EMAIL PROTECTED]> > >To: "Maven Users List" <[EMAIL PROTECTED]> > >Sent: Sunday, July 04, 2004 9:19 PM > >Subject: Re: Maven Goals within Eclipse Debug environment? > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey [EMAIL PROTECTED] CommonJava Open Components Project http://www.commonjava.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
