maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joakim Erdfelt (JIRA)" <>
Subject [jira] Created: (MRM-613) [FEATURE] Archiva ArtifactRank
Date Mon, 03 Dec 2007 18:23:57 GMT
[FEATURE] Archiva ArtifactRank

                 Key: MRM-613
             Project: Archiva
          Issue Type: New Feature
          Components: reporting
    Affects Versions: 1.1
            Reporter: Joakim Erdfelt

This is a new feature request.

ArtifactRank (the Archiva version of Googles PageRank)

I'd like to see some badging of the health of the artifact, encourage the proper creation
of artifacts this way.  We can provide a graphic on the artifact page (and even the artifact
search results and browse screens).  This rank can also be used to increase the importance
of hits on the search results.

      100% = Gold Award for excellence.
70% to 99% = Green Award  (Good)
40% to 69% = Yellow Award (Warning)
 0% to 39% = Red Badge    (Warning++)

* How many other projects use the artifact. (junit would be highly ranked)
* License is fully defined.
* License file exists in the artifact archive.
* URL is defined.
* At least 1 contact point is defined. (Developer email address or mailing list)
* A POM is defined.
* Checksums are defined.
* The maven pom manifest information exists.
* All dependencies exist in the repository too.
* All parent poms exist in the repository too.
* All plugins used exist in the repository too.
* If the artifact contains java ...
** All of the *.class files are within the same groupId that is defined in the POM.
   This is to indicate bad deployment, or bad
** All of the declared imports have an associated dependency defined.
** The file contains the version specified.
** The source.jar exists.
** The javadoc.jar exists.

This list of checks can feed the reporting too.
And the list of checks should be able to be extended / enhanced by administrators of Archiva
installs too.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message