[ 
http://jira.codehaus.org/browse/MRM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107618
 ] 

Teodoro Cue Jr. commented on MRM-505:
-------------------------------------

The examples in the description (a) (b) (c) are described in MRM-506.

As for the rest ...
d) The number of source files? Do you mean the compressed / embedded source 
files in the *-sources.jar artifacts?
e) "Metadata" is too vague. Do you mean .pom, maven-metadata.xml, 
maven-metadata-.xml, *-site.xml, or any of the other 'metadata' files?
f) License Type is hard to do ATM, we need to create a LicenseTypeMapper lib 
first, as all license definitions are pretty much free-form, this would mean 
the mapping that the LicenseTypeMapper needs to be saved / stored in the 
database, and also screens need to be created that the admin / user can utilize 
to manage the mapping of the freeform definitions to a known license type.
g) The concept of "related" needs more a more clear (precise) definition.

> Ability to Aggregate/Report on a variety of artifact criterium
> --------------------------------------------------------------
>
>                 Key: MRM-505
>                 URL: http://jira.codehaus.org/browse/MRM-505
>             Project: Archiva
>          Issue Type: New Feature
>          Components: reporting
>            Reporter: Teodoro Cue Jr.
>
> In addition to basic summary information on the total # of files in the 
> Maestro Repository Manager (MRM) - we need to support the following other 
> basic summary information:
> a) number of unique/discrete projects (based on combo of GroupID and 
> ArtifactID - or is it just ArtifactID)
> b) number of unique community/company projects (based on GroupID)
> c) number of wars, jars, ears, etc. (by file extension type)
> d) number of source files
> e) number of metadata files
> f) number of artifacts w/ a certain license type (also number of artifacts 
> with no license info)
> g) number of projects RELATED to a unique community/company
> there are other stats, but they are more historical, qualitative vs. 
> quantitative - should I put them all here? or separate as another issue?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to