You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/04/08 14:32:00 UTC
[jira] [Issue Comment Deleted] (MPIR-367) Remove Dependency
Repository Locations from dependency report
[ https://issues.apache.org/jira/browse/MPIR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MPIR-367:
--------------------------------
Comment: was deleted
(was: Build failed in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #7
See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/7/)
> Remove Dependency Repository Locations from dependency report
> -------------------------------------------------------------
>
> Key: MPIR-367
> URL: https://issues.apache.org/jira/browse/MPIR-367
> Project: Maven Project Info Reports Plugin
> Issue Type: Task
> Components: dependencies
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.0
>
>
> The final section of the dependency page can contain a list of the repositories and for every artifact it can show if it is available in that repository. This is controlled by the {{dependencyLocationsEnabled}} parameter.
> This section is blocking a clean migration to Maven 3 only. Besides that it might give false assumptions, because it doesn't verify if all artifacts are the some (not just by name).
> So for now let's remove this section. If the community wants it back we can reconsider this decision.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)