Re. this. Is there anything you want changed on it? Any designs/features? I'm looking for something to do over the weekend. I have to do a certain amount of programming to keep my emotional level high :>
As you also probably noticed, I heavily commented it. I tried to explain what everything does. It's a bit over the top, but the JUnit runner design isn't very flexible if you want to keep to good OOP principals. A lot of innovation and maturity will be needed to have it even close to as modular/flexible as OpenEJB. So to accommodate for this I added many comments to describe it. It's not a very nice design. It works, though I keep feeling like it's a mess, and wanting to rewrite it. Though, it's difficult to think of ways to keep it modular and extensible without too much effort from the user into using it. Quintin Beukes On Fri, Oct 30, 2009 at 10:08 PM, Quintin Beukes <[email protected]>wrote: > Sorry, meant to send this to the list. > > > ---------- Forwarded message ---------- > From: Quintin Beukes <[email protected]> > Date: Fri, Oct 30, 2009 at 10:06 PM > Subject: Re: JUnit Runner 0.1 > To: David Blevins <[email protected]> > > > re. this. > > As you probably noticed the source formatting is very different from that > of OpenEJB. Eclipse has a code formatter/cleanup feature. Feel free to run > it and reformat the code according to OpenEJB standards. > > I'm not used to developing in other styles. Where ever I work the styles > are usually decided by myself, so I'm used to a certain style. Whenever I > work on Geronimo/OpenEJB code I keep having to reformat when I notice this. > Having worked from a clean code base for the JUnit runner there wasn't any > reminders. I actually only thought of it now when I jumped into the source > code. > > Quintin Beukes > > >
