[ http://jira.codehaus.org/browse/MPIR-55?page=all ]
Joakim Erdfelt updated MPIR-55:
-------------------------------
Attachment: MPIR-55-dependencies-details-and-repo-locations.diff
Added the ability to disable the 2 new sections.
parameters (with defaults)
* dependency.details.enabled = true
* dependency.locations.enabled = true
The timings for running this patch against MPIR itself.
Both enabled : 1m 29s
Details disabled: 1m 17s
Locations disabled: 48s
Both disabled: 42s
As you can tell from the example report at
http://joakim.erdfelt.com/maven-project-info-reports-plugin/dependencies.html
the repository locations aspect helps identify dependencies that do not exist
in a remote repository at this moment.
Another use case would be those organizations that have a very
compartmentalized repository setup with categories like (snapshot, release,
sandbox, proprietary). In this type of organiztion, when a project moves from
the sandbox, it is useful to know what dependencies it is using from the
sandbox repository also, so a complete transition can take place.
> Detailed Artifact Information & Repository Location for each Dependency.
> ------------------------------------------------------------------------
>
> Key: MPIR-55
> URL: http://jira.codehaus.org/browse/MPIR-55
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: New Feature
> Reporter: Joakim Erdfelt
> Fix For: 2.1
>
> Attachments: MPIR-55-dependencies-details-and-repo-locations.diff,
> mpir-dependencies-details-and-repo-locations.diff
>
>
> I've created a patch that uses MNG-2489 (maven-shared-jar) and WAGON-58
> (wagon provider improvements) to increase the level of information about the
> dependencies on the dependencies report.
> Example Report:
> http://joakim.erdfelt.com/maven-project-info-reports-plugin/dependencies.html
> (See sections titled "Dependency File Details" and "Dependency Repository
> Locations")
> This adds the following information about each dependency.
> * File size
> * Count of entries
> * Count of classes
> * Count of packages
> * JDK Revision of compiled classes
> * If Debug is Present in compiled classes.
> * If Jar is Sealed (in the manifest)
> * What Repository the artifact can be found in
> And adds a small section of all of the repositories in use by the project.
--
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
