[
https://issues.apache.org/jira/browse/MDEP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829951#comment-17829951
]
ASF GitHub Bot commented on MDEP-425:
-------------------------------------
slawekjaranowski commented on PR #51:
URL:
https://github.com/apache/maven-dependency-plugin/pull/51#issuecomment-2015646839
@pmoerenhout and other thanks for efforts ... we should not use
maven-artifact-transfer at all
It should be reimplemented with using direct resolver API like I did in #301
So I close it now.
> dependency:list-repositories ignores pluginRepository (only lists repository)
> -----------------------------------------------------------------------------
>
> Key: MDEP-425
> URL: https://issues.apache.org/jira/browse/MDEP-425
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: list-repositories
> Reporter: Michael Vorburger
> Priority: Major
>
> http://maven.apache.org/plugins/maven-dependency-plugin/list-repositories-mojo.html
> can be very useful! But unless we've missed something, it seems to only
> gather & list all <repositories><repository> but doesn't know about / ignores
> any <pluginRepositories><pluginRepository> ?
> What I'm suggesting is more that something like 'mvn
> org.apache.maven.plugins:maven-dependency-plugin:2.8:list-repositories' also
> lists plugin repositories (with an indication of which is a plugin vs. a
> dependency plug-in?) than a new list-plugin-repositories goal (just because I
> think in practice one would typically want to see both).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
