You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by kh...@apache.org on 2020/05/01 17:32:28 UTC
[maven-dependency-plugin] branch MDEP-660 created (now 6adc71c)
This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a change to branch MDEP-660
in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git.
at 6adc71c [MDEP-660] - Obsolete example of -Dverbose on web page
This branch includes the following new commits:
new 6adc71c [MDEP-660] - Obsolete example of -Dverbose on web page
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[maven-dependency-plugin] 01/01: [MDEP-660] - Obsolete example of
-Dverbose on web page
Posted by kh...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
khmarbaise pushed a commit to branch MDEP-660
in repository https://gitbox.apache.org/repos/asf/maven-dependency-plugin.git
commit 6adc71cceb0cc8bfc05d0b6d1ff72652d7e39f33
Author: Karl Heinz Marbaise <kh...@apache.org>
AuthorDate: Fri May 1 19:32:20 2020 +0200
[MDEP-660] - Obsolete example of -Dverbose on web page
---
...solving-conflicts-using-the-dependency-tree.apt | 64 ----------------------
src/site/site.xml | 1 -
2 files changed, 65 deletions(-)
diff --git a/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt b/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt
deleted file mode 100644
index 6e1c5e5..0000000
--- a/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt
+++ /dev/null
@@ -1,64 +0,0 @@
-~~ Licensed to the Apache Software Foundation (ASF) under one
-~~ or more contributor license agreements. See the NOTICE file
-~~ distributed with this work for additional information
-~~ regarding copyright ownership. The ASF licenses this file
-~~ to you under the Apache License, Version 2.0 (the
-~~ "License"); you may not use this file except in compliance
-~~ with the License. You may obtain a copy of the License at
-~~
-~~ http://www.apache.org/licenses/LICENSE-2.0
-~~
-~~ Unless required by applicable law or agreed to in writing,
-~~ software distributed under the License is distributed on an
-~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~~ KIND, either express or implied. See the License for the
-~~ specific language governing permissions and limitations
-~~ under the License.
-
- ------
- Resolving conflicts using the dependency tree
- ------
- Mark Hobson
- ------
- 2007-09-01
- ------
-
-Resolving conflicts using the dependency tree
-
- A project's dependency tree can be expanded to display dependency conflicts. For example, to find out why Commons
- Collections 2.0 is being used by the Maven Dependency Plugin, we can execute the following in the project's
- directory:
-
-+---+
-mvn dependency:tree -Dverbose -Dincludes=commons-collections
-+---+
-
- The <<<verbose>>> flag instructs the dependency tree to display conflicting dependencies that were omitted from the
- resolved dependency tree. In this case, the goal outputs:
-
-+---+
-[INFO] [dependency:tree]
-[INFO] org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0-alpha-5-SNAPSHOT
-[INFO] +- org.apache.maven.reporting:maven-reporting-impl:jar:2.0.4:compile
-[INFO] | \- commons-validator:commons-validator:jar:1.2.0:compile
-[INFO] | \- commons-digester:commons-digester:jar:1.6:compile
-[INFO] | \- (commons-collections:commons-collections:jar:2.1:compile - omitted for conflict with 2.0)
-[INFO] \- org.apache.maven.doxia:doxia-site-renderer:jar:1.0-alpha-8:compile
-[INFO] \- org.codehaus.plexus:plexus-velocity:jar:1.1.3:compile
-[INFO] \- commons-collections:commons-collections:jar:2.0:compile
-+---+
-
- Thus we can see that Commons Collections 2.0 was chosen over 2.1 since it is nearer, and by default Maven resolves
- version conflicts with a nearest-wins strategy.
-
- More specifically, in verbose mode the dependency tree shows dependencies that were omitted for: being a duplicate
- of another; conflicting with another's version and/or scope; and introducing a cycle into the dependency tree.
-
-* Verbose flag support in 3.0+ version
-
- Support for <<<verbose>>> flag has been removed since maven-dependency-plugin 3.0 ({{{https://issues.apache.org/jira/browse/MDEP-494}MDEP-494}}).
- Extra output can be obtained by using an older version until proper support is reintroduced.
-
-+---+
-mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:tree -Dverbose=true
-+---+
diff --git a/src/site/site.xml b/src/site/site.xml
index 7cc2944..afec97a 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -42,7 +42,6 @@ under the License.
<item name="Failing the build on dependency analysis warnings" href="examples/failing-the-build-on-dependency-analysis-warnings.html"/>
<item name="Exclude Dependencies from Dependency Analysis" href="examples/exclude-dependencies-from-dependency-analysis.html"/>
<item name="Filtering the dependency tree" href="examples/filtering-the-dependency-tree.html"/>
- <item name="Resolving conflicts using the dependency tree" href="examples/resolving-conflicts-using-the-dependency-tree.html"/>
<item name="Purging local repository dependencies" href="examples/purging-local-repository.html"/>
</menu>
<menu name="Resources">