Update Checker Framework URLs to https://checkerframework.org/

README.txt

@@ -7,5 +7,5 @@ It appears in this repository (after you run `make -C docs/manual`):
 
 Prebuilt versions also appear on the web:
 
-  * HTML: http://checker-framework.com/manual/
-  * PDF: http://checker-framework.com/manual/checker-framework-manual.pdf
+  * HTML: https://checkerframework.org/manual/
+  * PDF: https://checkerframework.org/manual/checker-framework-manual.pdf

changelog.txt

@@ -1,7 +1,8 @@
 Version 2.1.8, 1 February 2017
 
-The Checker Framework webpage has moved to http://checker-framework.org/.
-Old URLs should redirect to the new one, but please update your links.
+The Checker Framework webpage has moved to https://checkerframework.org/.
+Old URLs should redirect to the new one, but please update your links
+and let us know if any old links are broken rather than redirecting.
 
 The documentation has been reorganized in the Checker Framework repository.
 The manual, tutorial, and webpages now appear under checker-framework/docs/.
@@ -247,7 +248,7 @@ Documentation:
 For type-system developers:
  * The org.checkerframework.framework.qual.TypeQualifier{s} annotations are
    now deprecated.  To indicate which annotations a checker supports, see
-   http://checker-framework.com/manual/#creating-indicating-supported-annotations .
+   https://checkerframework.org/manual/#creating-indicating-supported-annotations .
    Support for TypeQualifier{s} will be removed in the next release.
  * Renamed
    org.checkerframework.framework.qual.Default{,Qualifier}ForUnannotatedCode to
@@ -840,7 +841,7 @@ Adapt to underlying jsr308-langtools changes.
   JDK 7 is now required.  The Checker Framework does not build or run on JDK 6.
 
 Documentation:
-  A new tutorial is available at http://checker-framework.com/tutorial/
+  A new tutorial is available at https://checkerframework.org/tutorial/
 
 ----------------------------------------------------------------------
 Version 1.5.0, 14 Jan 2013
@@ -1378,7 +1379,7 @@ Eclipse support:
   different repository
   (http://code.google.com/a/eclipselabs.org/p/checker-plugin/) but a user
   obtains it from the same URL as before:
-  http://checker-framework.com/eclipse/
+  https://checkerframework.org/eclipse/
 
 Property Key Checker:
   The property key checker allows multiple resource bundles and the
@@ -2086,7 +2087,7 @@ Manual
     8  Annotating libraries
     9  How to create a new checker plugin
   Javadoc for the Checker Framework is included in its distribution and is
-    available online at http://checker-framework.com/api/ .
+    available online at https://checkerframework.org/api/ .
 
 ----------------------------------------------------------------------
 Version 0.6.4, 9 June 2008

checker/bin/README

@@ -21,7 +21,7 @@ checker.jar - Contains all the Checker Framework classes including the framework
 itself, all built-in checkers, and the annotations found in checker-qual.jar.
 
 javac.jar - Contains the Type Annotations Compiler
-(see http://checker-framework.com/README-jsr308.html)
+(see https://checkerframework.org/README-jsr308.html)
 
 jdk<x>.jar - Each jdk<x>.jar, where <x> is a major java version (e.g., 6, 7,
 8, or 9), contains a version of the OpenJDK annotated with Checker Framework
@@ -33,4 +33,4 @@ all versions of jdk<x>.jar by running "ant all.jdks.jar".
 maven-plugin/poms - this directory contains Maven POM files for each of the
 jars that is found in the dist directory.  These POMs are used to deploy each
 jar as a Maven artifact to the
-http://checker-framework.com/m2-repo/ maven repository.
+https://checkerframework.org/m2-repo/ maven repository.

checker/build.xml

@@ -383,7 +383,7 @@
             <manifest>
                 <attribute name="Main-Class" value="org.checkerframework.framework.util.CheckerMain"/>
                 <attribute name="Implementation-Version" value="${build.version}"/>
-                <attribute name="Implementation-URL" value="http://checker-framework.com/"/>
+                <attribute name="Implementation-URL" value="https://checkerframework.org/"/>
             </manifest>
         </jar>
     </target>
@@ -464,14 +464,14 @@
         <jar destfile="${checker.qual.lib}" basedir="${checker-qual-classes-tmp}">
             <manifest>
                 <attribute name="Implementation-Version" value="${build.version}"/>
-                <attribute name="Implementation-URL" value="http://checker-framework.com/"/>
+                <attribute name="Implementation-URL" value="https://checkerframework.org/"/>
             </manifest>
         </jar>
 
         <jar destfile="${checker.qual.sources.lib}" basedir="${checker-qual-sources-tmp}">
             <manifest>
                 <attribute name="Implementation-Version" value="${build.version}"/>
-                <attribute name="Implementation-URL" value="http://checker-framework.com/"/>
+                <attribute name="Implementation-URL" value="https://checkerframework.org/"/>
             </manifest>
         </jar>
         <delete dir="${checker-qual-sources-tmp}" failonerror="false"/>
@@ -568,15 +568,15 @@
         <jar destfile="${checker.compat.qual.lib}" basedir="${checker-compat-qual-classes-tmp}">
             <manifest>
                 <attribute name="Implementation-Version" value="${build.version}"/>
-                <attribute name="Implementation-URL" value="http://checker-framework.com/"/>
+                <attribute name="Implementation-URL" value="https://checkerframework.org/"/>
             </manifest>
         </jar>
 
         <jar destfile="${checker.compat.qual.sources.lib}"
              basedir="${checker-compat-qual-sources-tmp}">
             <manifest>
                 <attribute name="Implementation-Version" value="${build.version}"/>
-                <attribute name="Implementation-URL" value="http://checker-framework.com/"/>
+                <attribute name="Implementation-URL" value="https://checkerframework.org/"/>
             </manifest>
         </jar>
         <delete dir="${checker-compat-qual-sources-tmp}" failonerror="false"/>
@@ -1531,7 +1531,7 @@ So, use our own archived version.
             description="Create the instrumented jdkX.jar using the JDK specified by JAVA_HOME">
       <property name="annotation-file-utilities.jar" value="${annotation.tools}/annotation-file-utilities/annotation-file-utilities.jar"/>
       <available property="annotation-file-utilities.exist" file="${annotation-file-utilities.jar}" />
-      <fail unless="annotation-file-utilities.exist" message="Could not find annotation-file-utilities.jar: ${annotation-file-utilities.jar}.  You must build Annotation Tools; see http://checker-framework.com/manual/#build-source" />
+      <fail unless="annotation-file-utilities.exist" message="Could not find annotation-file-utilities.jar: ${annotation-file-utilities.jar}.  You must build Annotation Tools; see https://checkerframework.org/manual/#build-source" />
 
       <exec executable="make" failonerror="true">
          <arg value="LANGTOOLS=${jsr308.langtools}"/>

checker/jdk/annotate-jdk.sh

@@ -157,13 +157,13 @@ stripDefs() {
 COMMENTS=0  # non-zero to enable
 if [ ${COMMENTS} -ne 0 ] ; then
 # download patch
-[ -r annotated-jdk-comment-patch.jaif ] || wget http://checker-framework.com/annotated-jdk-comment-patch.jaif || exit $?
+[ -r annotated-jdk-comment-patch.jaif ] || wget https://checkerframework.org/annotated-jdk-comment-patch.jaif || exit $?
 (cd "${JDK}" && patch -p1 < annotated-jdk-comment-patch.jaif)
 fi
 
 # download annotation definitions
 [ -r annotation-defs.jaif ]\
- || wget http://checker-framework.com/annotation-defs.jaif\
+ || wget https://checkerframework.org/annotation-defs.jaif\
  || exit $?
 
 

checker/src/javax/annotation/concurrent/GuardedBy.java

@@ -24,7 +24,7 @@
     /**
      * The Java expressions that need to be held.
      *
-     * @see <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">Syntax of
+     * @see <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">Syntax of
      *     Java expressions</a>
      */
     String[] value() default {};

checker/src/net/jcip/annotations/GuardedBy.java

@@ -24,7 +24,7 @@
     /**
      * The Java expressions that need to be held.
      *
-     * @see <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">Syntax of
+     * @see <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">Syntax of
      *     Java expressions</a>
      */
     String[] value() default {};

checker/src/org/checkerframework/checker/interning/InterningVisitor.java

@@ -69,7 +69,7 @@ public InterningVisitor(BaseTypeChecker checker) {
     /**
      * @return true if interning should be verified for the input expression. By default, all
      *     classes are checked for interning unless {@code -Acheckclass} is specified.
-     * @see <a href="http://checker-framework.com/manual/#interning-checks">What the Interning
+     * @see <a href="https://checkerframework.org/manual/#interning-checks">What the Interning
      *     Checker checks</a>
      */
     private boolean shouldCheckExpression(ExpressionTree tree) {

checker/src/org/checkerframework/checker/lock/qual/EnsuresLockHeld.java

@@ -26,7 +26,7 @@
     /**
      * The Java expressions whose values are held after the method terminates successfully.
      *
-     * @see <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">Syntax of
+     * @see <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">Syntax of
      *     Java expressions</a>
      */
     String[] value();

checker/src/org/checkerframework/checker/lock/qual/EnsuresLockHeldIf.java

@@ -27,7 +27,7 @@
     /**
      * Java expressions whose values are held after the method returns the given result.
      *
-     * @see <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">Syntax of
+     * @see <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">Syntax of
      *     Java expressions</a>
      */
     String[] expression();

checker/src/org/checkerframework/checker/lock/qual/GuardedBy.java

@@ -33,7 +33,7 @@
  * <p>{@code @GuardedBy({})} is the default type qualifier.
  *
  * <p>The argument is a string or set of strings that indicates the expression(s) that must be held,
- * using the <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">syntax of
+ * using the <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">syntax of
  * Java expressions</a> described in the manual. The expressions evaluate to an intrinsic (built-in,
  * synchronization) monitor or an explicit {@link java.util.concurrent.locks.Lock}. The expression
  * {@code "<self>"} is also permitted; the type {@code @GuardedBy("<self>") Object o} indicates that
@@ -73,7 +73,7 @@
     /**
      * The Java value expressions that need to be held.
      *
-     * @see <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">Syntax of
+     * @see <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">Syntax of
      *     Java expressions</a>
      */
     String[] value() default {};

checker/src/org/checkerframework/checker/lock/qual/Holding.java

@@ -12,7 +12,7 @@
  * is invoked.
  *
  * <p>The argument is a string or set of strings that indicates the expression(s) that must be held,
- * using the <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">syntax of
+ * using the <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">syntax of
  * Java expressions</a> described in the manual. The expressions evaluate to an intrinsic (built-in,
  * synchronization) monitor, or an explicit {@link java.util.concurrent.locks.Lock}.
  *
@@ -28,7 +28,7 @@
     /**
      * The Java expressions that need to be held.
      *
-     * @see <a href="http://checker-framework.com/manual/#java-expressions-as-arguments">Syntax of
+     * @see <a href="https://checkerframework.org/manual/#java-expressions-as-arguments">Syntax of
      *     Java expressions</a>
      */
     String[] value();

checker/src/org/checkerframework/checker/nullness/AbstractNullnessChecker.java

@@ -21,7 +21,7 @@
     // which is allowed by default.
     // Forbidding is sound and will eventually be the default.
     // Allowing is unsound, as described in Section 3.3.4, "Nullness and arrays":
-    //     http://checker-framework.com/manual/#nullness-arrays
+    //     https://checkerframework.org/manual/#nullness-arrays
     // It is the default temporarily, until we improve the analysis to reduce false positives or we
     // learn what advice to give programmers about avoid false positive warnings.
     // See issue #986: https://github.com/typetools/checker-framework/issues/986

checker/src/org/checkerframework/checker/regex/RegexUtil.java

@@ -17,7 +17,7 @@
  * expression.
  *
  * <p>For an example of intended use, see section <a
- * href="http://checker-framework.com/manual/#regexutil-methods">Testing whether a string is a
+ * href="https://checkerframework.org/manual/#regexutil-methods">Testing whether a string is a
  * regular expression</a> in the Checker Framework manual.
  *
  * <p><b>Runtime Dependency</b>: Using this class introduces a runtime dependency. This means that

checker/tests/nullness-extra/shorthand/README

@@ -1,5 +1,5 @@
 This is a test of the "checker shorthand" feature.
-See: http://checker-framework.com/manual/#shorthand-for-checkers
+See: https://checkerframework.org/manual/#shorthand-for-checkers
 This test is not Nullness specific.
 
 We have placed this test in this location because it has two preconditions:

docs/checker-framework-quick-start.html

@@ -15,12 +15,12 @@ <h1>Checker Framework quick start guide</h1>
 
 <p>
 A pluggable type-checker, or &ldquo;checker&rdquo; for short, prevents certain run-time errors.  For example, it can prove that your code never suffers a
-NullPointerException.  Choose which checker you want to run from the <a href="http://checker-framework.com/manual/#introduction">list
+NullPointerException.  Choose which checker you want to run from the <a href="https://checkerframework.org/manual/#introduction">list
 of checkers</a>.
 </p>
 
 <p>
-To <a href="http://checker-framework.com/manual/#installation">install the Checker Framework</a>, download and unzip
+To <a href="https://checkerframework.org/manual/#installation">install the Checker Framework</a>, download and unzip
 the Checker Framework distribution:
 <a href="checker-framework-2.1.7.zip"><!-- checker-framework-zip-version -->checker-framework-2.1.7.zip<!-- /checker-framework-zip-version --></a>.<br/>
 Or, the
@@ -29,7 +29,7 @@ <h1>Checker Framework quick start guide</h1>
 </p>
 
 <p>
-To <a href="http://checker-framework.com/manual/#running">run a checker</a>, supply the <code>-processor</code> command-line argument:
+To <a href="https://checkerframework.org/manual/#running">run a checker</a>, supply the <code>-processor</code> command-line argument:
 </p>
 
 <pre>
@@ -38,7 +38,7 @@ <h1>Checker Framework quick start guide</h1>
 
 <p>
 You write annotations in your code.  Then, the checker
-<a href="http://checker-framework.com/manual/#checker-guarantees">verifies
+<a href="https://checkerframework.org/manual/#checker-guarantees">verifies
 two facts:</a> (1) the annotations you wrote are correct (they are consistent with your source code), and (2) your program will not suffer certain exceptions or errors at run time.
 </p>
 
@@ -56,7 +56,7 @@ <h1>Checker Framework quick start guide</h1>
 <code>""</code>, but does not include <code>null</code>.
 <br/>
 You write a type annotation right before a use of a type (on the same
-line), <a href="http://checker-framework.com/manual/#writing-annotations">as in</a>:
+line), <a href="https://checkerframework.org/manual/#writing-annotations">as in</a>:
 <pre>
   @NonNull String s;
   List&lt;@Positive Integer&gt; l;
@@ -81,27 +81,27 @@ <h1>Checker Framework quick start guide</h1>
 
 <p>
 For the most part, you only need to write annotations on method signatures and fields.
-Most annotations within method bodies are <a href="http://checker-framework.com/manual/#type-refinement">inferred for you automatically</a>.
+Most annotations within method bodies are <a href="https://checkerframework.org/manual/#type-refinement">inferred for you automatically</a>.
 Furthermore, each checker applies certain defaults to further reduce your
 annotation burden; for example, using the
-<a href="http://checker-framework.com/manual/#nullness-checker">Nullness
+<a href="https://checkerframework.org/manual/#nullness-checker">Nullness
   Checker</a>, you do not need to write <code>@NonNull</code>, only
   <code>@Nullable</code> which appears less often.
 See the manual for more
-<a href="http://checker-framework.com/manual/#tips-about-writing-annotations">tips
+<a href="https://checkerframework.org/manual/#tips-about-writing-annotations">tips
   about writing annotations</a>.
 </p>
 
 <p>
 To learn more, you can read:
 </p>
 <ul>
-  <li><a href="http://checker-framework.com/tutorial/">Checker Framework tutorial</a>
+  <li><a href="https://checkerframework.org/tutorial/">Checker Framework tutorial</a>
   </li>
   <li><a href="https://github.com/glts/safer-spring-petclinic/wiki">Nullness Checker tutorial</a></li>
-  <li><a href="http://checker-framework.com/manual/#faq">Checker Framework frequently asked questions (FAQs)</a>
+  <li><a href="https://checkerframework.org/manual/#faq">Checker Framework frequently asked questions (FAQs)</a>
   </li>
-  <li><a href="http://checker-framework.com/manual/">Checker Framework manual</a>
+  <li><a href="https://checkerframework.org/manual/">Checker Framework manual</a>
   </li>
 </ul>
 

docs/manual/annotating-libraries.tex

@@ -92,7 +92,7 @@ \section{Creating an annotated library\label{annotated-libraries-creating}}
   % library.  You would express the annotations textually, typically as an
   % annotation index file, and
   % then insert them in the library by using the Annotation File Utilities
-  % (\myurl{http://checker-framework.com/annotation-file-utilities/}).
+  % (\myurl{https://checkerframework.org/annotation-file-utilities/}).
   % See the Annotation File Utilities documentation for full details.
 
   With this compilation approach, the syntax of the library annotations is

docs/manual/creating-a-checker.tex

@@ -63,7 +63,7 @@ \chapter{How to create a new checker\label{creating-a-checker}}
 of those.
 The Javadoc documentation of the framework and the checkers is in the
 distribution and is also available online at
-\myurl{http://checker-framework.com/api/}.
+\myurl{https://checkerframework.org/api/}.
 
 If you write a new checker and wish to advertise it to the world, let us
 know so we can mention it in the Checker Framework Manual, link to
@@ -104,10 +104,10 @@ \section{How checkers build on the Checker Framework\label{creating-tool-relatio
 Other \par tools
 \\ \hline
 \multicolumn{6}{|p{6\bw}|}{\centering Checker Framework \par (enables creation of pluggable type-checkers)} &
-\multicolumn{2}{p{3\bw}|}{\centering \href{http://checker-framework.com/annotation-file-utilities/}{Annotation File Utilities} \par (\code{.java} $\leftrightarrow$ \code{.class} files)}
+\multicolumn{2}{p{3\bw}|}{\centering \href{https://checkerframework.org/annotation-file-utilities/}{Annotation File Utilities} \par (\code{.java} $\leftrightarrow$ \code{.class} files)}
 \\ \hline
 \multicolumn{8}{|p{8.5\bw}|}{\centering
-  \href{http://checker-framework.com/jsr308/}{Type Annotations} syntax
+  \href{https://checkerframework.org/jsr308/}{Type Annotations} syntax
   and classfile format (``JSR 308'') \par \centering (no built-in semantics)} \\ \hline
 \end{tabular}
 \end{center}
@@ -899,7 +899,7 @@ \section{Dataflow: enhancing flow-sensitive type qualifier inference\label{creat
 The Checker Framework's type refinement is implemented with a dataflow algorithm
 which can be customized to enhance the built-in type refinement. The next
 sections detail dataflow customization.  It would also be helpful to read the
-\href{http://checker-framework.com/manual/checker-framework-dataflow-manual.pdf}
+\href{https://checkerframework.org/manual/checker-framework-dataflow-manual.pdf}
 {Dataflow Manual}, which gives a more in-depth description of the Checker
 Framework's dataflow framework.