Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(doc) - Add note on dependecy:tree -Dverbose support in 3.0+ #4

Merged
merged 1 commit into from
Mar 1, 2020
Merged

(doc) - Add note on dependecy:tree -Dverbose support in 3.0+ #4

merged 1 commit into from
Mar 1, 2020

Conversation

grimsa
Copy link
Contributor

@grimsa grimsa commented Sep 10, 2018

Running mvn dependency:tree -Dverbose as suggested in docs produces non-verbose output and the following warning:

[INFO] --- maven-dependency-plugin:3.0.0:tree (default-cli) @ my-project ---
[INFO] Verbose not supported since maven-dependency-plugin 3.0
...

From what I gather, it was originally reported as MDEP-374 back in 2.8, then a workaround based on Maven2 was introduced only to be removed later with MDEP-494.

This PR updates documentation with a possible workaround.

--

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue 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.
  • Each commit in the pull request should have a meaningful subject line and body.
  • 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.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • 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 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
you have to acknowledge this by using the following check-box.

@khmarbaise
Copy link
Member

Hi, could you please so kind to rebase your PR against most recent master. I appreciate to merge you PR....

@khmarbaise khmarbaise self-assigned this Jan 4, 2019
@grimsa
Copy link
Contributor Author

grimsa commented Jan 4, 2019

Rebased on master.
Also updated the suggestion to use an older version of the plugin instead of debug flag (-X ).

@elharo elharo merged commit 2284376 into apache:master Mar 1, 2020
asfgit pushed a commit that referenced this pull request Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants