You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/17 19:06:00 UTC
[jira] [Commented] (MDEP-425) dependency:list-repositories ignores
pluginRepository (only lists repository)
[ https://issues.apache.org/jira/browse/MDEP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584288#comment-16584288 ]
ASF GitHub Bot commented on MDEP-425:
-------------------------------------
mattnelson opened a new pull request #3: [MDEP-425] - Add list-plugin-repositories goal
URL: https://github.com/apache/maven-dependency-plugin/pull/3
https://issues.apache.org/jira/browse/MDEP-425
Replacement PR for https://github.com/apache/maven-plugins/pull/113
Add list-plugin-repositories goal to supplement the list-repositories goal.
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MDEP) filed
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line and body.
- [x] Format the pull request title like `[MDEP-XXX] - Fixes bug in ApproximateQuantiles`,
where you replace `MDEP-XXX` with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
- [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> 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
> 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
(v7.6.3#76005)