diff --git a/sql/catalyst/pom.xml b/sql/catalyst/pom.xml
index 36948ba52b0641639bb01915569991b73dc3ed16..0bbf7a95124cfee1e7d009a9915634c36b41a2cc 100644
--- a/sql/catalyst/pom.xml
+++ b/sql/catalyst/pom.xml
@@ -109,7 +109,7 @@
            so that the tests classes of external modules can use them. The two execution profiles
            are necessary - first one for 'mvn package', second one for 'mvn test-compile'. Ideally,
            'mvn compile' should not compile test classes and therefore should not need this.
-           However, an open Maven bug (http://jira.codehaus.org/browse/MNG-3559)
+           However, a closed due to "Cannot Reproduce" Maven bug (https://issues.apache.org/jira/browse/MNG-3559)
            causes the compilation to fail if catalyst test-jar is not generated. Hence, the
            second execution profile for 'mvn test-compile'.
       -->
diff --git a/sql/core/pom.xml b/sql/core/pom.xml
index 7327c9b0c9c50ff064b1e623d8299fcf23400822..1bc34a6b069d9cc4c263abd9afda8a5dd4627cae 100644
--- a/sql/core/pom.xml
+++ b/sql/core/pom.xml
@@ -161,7 +161,7 @@
             so that the tests classes of external modules can use them. The two execution profiles
             are necessary - first one for 'mvn package', second one for 'mvn test-compile'. Ideally,
             'mvn compile' should not compile test classes and therefore should not need this.
-            However, an open Maven bug (http://jira.codehaus.org/browse/MNG-3559)
+            However, a closed due to "Cannot Reproduce" Maven bug (https://issues.apache.org/jira/browse/MNG-3559)
             causes the compilation to fail if catalyst test-jar is not generated. Hence, the
             second execution profile for 'mvn test-compile'.
       -->