Philip,

In my investigation of HACK-719 (http://hackydev.ics.hawaii.edu:8080/browse/HACK-719), I've found that the DailyProjectCoverage isInProject(Coverage, User) method to be a pretty good design pattern for handling the backwards compatibility of ProjectJavaClassWorkspaceMap. I plan on writing a similar method to solve the HACK-719 bug. It seems to me that all DailyProject implementations that previously used the ProjectJavaClassWorkspaceMap should have a method like this.

I've also noticed some problems with the Dependency data and its associated DailyProject implementation (DailyProjectDependency2). We are sending Dependency data but I haven't seen it in the Daily Project Details alert or analysis. I've also seen some Dependency data that has a null path attribute:

<entry runTime="1148814469318" granularity="class" tool="DependencyFinder" path="null" tstamp="1148814632064" outbound="" inbound="" pMap="0000" /> <entry runTime="1148814469318" granularity="class" tool="DependencyFinder" path="null" tstamp="1148814509613" outbound="" inbound="org.hackystat.app.cgqm.implementation.MHackystatDataAccess,org.hackystat.app.cgqm.implementation.TestMTelemetryAccess" pMap="0000" />

I created issues for these: http://hackydev.ics.hawaii.edu:8080/browse/HACK-727 and http://hackydev.ics.hawaii.edu:8080/browse/HACK-728

thanks, Aaron

At 06:30 PM 5/30/2006, Philip Johnson wrote:
Yes, this is a natural result of us having been in the 'exploration' phase with respect to DailyProjectData design. I think we've now gained enough experience in enough different situations that we can begin to standardize the way it should work. That will be an upcoming bit of work, probably within two releases.

Cheers,
Philip

----- Original Message -----
From: Aaron Akihisa Kagawa <[EMAIL PROTECTED]>
Date: Wednesday, May 31, 2006 1:48 am
Subject: Re: [HACKYSTAT-DEV-L] DailyProject FileMetrics bug(s) diagnosed
To: Philip Johnson <[EMAIL PROTECTED]>
Cc: [email protected]

> In addition, the problem that I am having is that
> DailyProjectCoverage doesn't work the same way the other
> DailyProject implementations work in respect to handeling "per
> module" sending of data. Thus, when I send coverage per module it
> wipes out my previous coverage snapshot.
>
> see http://hackydev.ics.hawaii.edu:8080/browse/HACK-387
>
> thanks, Aaron
>
>
> ----- Original Message -----
> From: Philip Johnson <[EMAIL PROTECTED]>
> Date: Thursday, May 25, 2006 1:22 am
> Subject: Re: [HACKYSTAT-DEV-L] DailyProject FileMetrics bug(s)
> diagnosedTo: [email protected]
>
> > > Hm. hold the phone. I think it does do the merging. I'll have
> to
> > > double check but I think I don't send all my FileMetric data in
> > one
> > > bunch.  I send it by module.
> >
> > You're right, as usual, Aaron.  Looking at the way the Hackystat
> > build system is constructed, the FileMetric data (both SCLC and
> > LOCC) is sent module-by-module.
> >
> > Cheers,
> > Philip
> >
>

Reply via email to