Was this a TimeZone issue? I wrote the TimeZoneChanger, so I guess I'm a little curious what is going on with the unit test failures that you are seeing. Okay.. I'll change my local computer's timezone and run the build. But, definitely clue me in to what you are having problems with.
thanks, Aaron ----- Original Message ----- From: Hongbing Kou <[EMAIL PROTECTED]> Date: Tuesday, August 22, 2006 2:50 pm Subject: Re: [HACKYSTAT-DEV-L] Help with a problem in DailyProjectCoverage2 (new DPD design) To: [email protected] > Hi, Aaron and Philip, > > I noticed that there was a unit test failure in > TestDailyProjectCoverage2, and fixed it with a little hack. Please > update your local copy before you add new things to it. > > Thanks, > Hongbing > > ----- Original Message ----- > From: Philip Johnson <[EMAIL PROTECTED]> > Date: Tuesday, August 22, 2006 8:53 am > Subject: Re: [HACKYSTAT-DEV-L] Help with a problem in > DailyProjectCoverage2 (new DPD design) > To: [email protected] > > > --On Monday, August 21, 2006 11:19 PM -1000 Aaron Kagawa > > <[EMAIL PROTECTED]> wrote: > > > > > The only problem that I see is that granularity supports wild > > cards, which makes little > > > sense. However, I'm estimating that it would probably take a > > while to remove that > > > functionality. Should I bother? Or just restrict the access to > > the methods that > > > provide the functionality to the outside world? > > > > If it's possible to have wild card granularity encapsulated as an > > internal implementation > > detail that is not exposed by the public API and never used in > > practice, then that would > > seem to me to be OK for now. As we do more of these DPD > redesigns, > > we may eventually > > figure out how the right way to refactor out the common code and > > that would help as well. > > > > Cheers, > > Philip > > >
