[maven-site] branch master updated: MNGSITE-399 Fix the `banned dependencies rule` link at `Optional Dependencies and Dependency Exclusions` (#142)

[el...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

elharo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 257212c  MNGSITE-399 Fix the `banned dependencies rule` link at `Optional Dependencies and Dependency Exclusions` (#142)
257212c is described below

commit 257212cab77babd6155ac9477fb7936a769458c7
Author: Edinson E. Padrón Urdaneta <EP...@users.noreply.github.com>
AuthorDate: Tue Mar 17 14:00:34 2020 -0500

    MNGSITE-399 Fix the `banned dependencies rule` link at `Optional Dependencies and Dependency Exclusions` (#142)
---
 .../introduction/introduction-to-optional-and-excludes-dependencies.apt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt b/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
index d777110..8a8c0e1 100644
--- a/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
+++ b/content/apt/guides/introduction/introduction-to-optional-and-excludes-dependencies.apt
@@ -314,7 +314,7 @@ Project-A
   
   If you truly want to ensure that a particular dependency appears nowhere in
   your classpath, regardless of path, the 
-  [banned dependencies rule](https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html)
+  {{{https://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html}banned dependencies rule}}
   can be configured to fail the build if a problematic dependency is found.
   When the build fails, you'll need to add specific exclusions on each path
   the enforcer finds.