From d425efd4957f849213d00b8cb87fb5390290c0c1 Mon Sep 17 00:00:00 2001
From: Alan Zimmer <48699787+alzimmermsft@users.noreply.github.com>
Date: Wed, 26 Feb 2020 11:15:45 -0800
Subject: [PATCH] Removed JavadocInlineTagCheck as it caused more issues than
 caught (#8485)

---
 .../src/main/resources/checkstyle/checkstyle.xml             | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/eng/code-quality-reports/src/main/resources/checkstyle/checkstyle.xml b/eng/code-quality-reports/src/main/resources/checkstyle/checkstyle.xml
index 9d3939dafd67a..965731f355bab 100755
--- a/eng/code-quality-reports/src/main/resources/checkstyle/checkstyle.xml
+++ b/eng/code-quality-reports/src/main/resources/checkstyle/checkstyle.xml
@@ -362,7 +362,10 @@ page at http://checkstyle.sourceforge.net/config.html -->
     1) Use {@codesnippet ...} instead of '<code>', '<pre>', or '{@code ...}' if these tags span multiple lines.
        Inline code sample are fine as-is.
     2) No check on class-level Javadoc. -->
-    <module name="com.azure.tools.checkstyle.checks.JavadocInlineTagCheck"/>
+    <!-- This check was removed as it causes more noise than fixes. The purpose of this check was to move away from -->
+    <!-- using <code>, <pre>, and {@code} tags while we were on-boarding codesnippets. These tags have since been   -->
+    <!-- removed and codesnippets are expected.                                                                     -->
+    <!-- <module name="com.azure.tools.checkstyle.checks.JavadocInlineTagCheck"/> -->
 
     <!-- CUSTOM CHECKS -->
     <!-- {@codesnippet ...} description should match naming pattern requirement below: