Fix mangled SCIP/SemanticDB doc references

Author: jupblb

README.md

@@ -1,4 +1,4 @@
-# Java and Kotlin indexer for [SCIP](https://github.com/sourcegraph/scip) ![](https://img.shields.io/badge/status-development-green?style=flat)
+# Java and Kotlin indexer for [SCIP](https://github.com/scip-code/scip) ![](https://img.shields.io/badge/status-development-green?style=flat)
 
 | Documentation        | Link                                                                   |
 | -------------------- | ---------------------------------------------------------------------- |

docs/design.md

@@ -5,10 +5,10 @@ title: Design
 
 This project is implemented as a
 [Java compiler plugin](https://docs.oracle.com/en/java/javase/11/docs/api/jdk.compiler/com/sun/source/util/Plugin.html)
-that generates one
-[SCIP](https://scalameta.org/docs/scip/specification.html) file for
-every `*.java` source file. After compilation completes, the SCIP files
-are processed to produce SCIP.
+that generates one partial
+[SCIP](https://github.com/scip-code/scip) index (a "shard") for
+every `*.java` source file. After compilation completes, the per-file SCIP
+shards are merged into a single SCIP index.
 
 ### Why Java compiler plugin?
 
@@ -25,20 +25,21 @@ There are several benefits to implementing scip-java as a compiler plugin:
   installed system dependencies, custom compiler options and custom annotation
   processors.
 
-### Why SCIP?
+### Why per-file SCIP shards?
 
-SCIP is Protobuf schema for information about symbols and types in Java
-programs and other languages. There are several benefits to using SCIP as
-an intermediary representation for SCIP:
+[SCIP](https://github.com/scip-code/scip) is a Protobuf schema for information
+about symbols and types in Java programs and other languages. There are several
+benefits to emitting one SCIP shard per source file and merging them afterwards:
 
 - **Simplicity**: It's easy to translate a single Java source file into a single
-  SCIP file inside a compiler plugin. It's more complicated to produce
-  SCIP because compiler plugins does not have access to a project-wide context,
-  which is necessary to produce accurate definitions and hovers in multi-module
-  projects with external library dependencies.
-- **Performance**: SCIP is fast to write and read. Each compilation unit
-  can be processed independently to keep memory usage low. The final conversion
-  from SCIP to SCIP can be safely parallelized.
+  SCIP shard inside a compiler plugin. It's more complicated to produce a
+  complete project-wide index directly because compiler plugins do not have
+  access to a project-wide context, which is necessary to produce accurate
+  definitions and hovers in multi-module projects with external library
+  dependencies.
+- **Performance**: SCIP shards are fast to write and read. Each compilation unit
+  can be processed independently to keep memory usage low. The final merge of
+  the shards into a single index can be safely parallelized.
 - **Cross-repository**: Compiler plugins have access to both source code and the
   classpath (compiled bytecode of upstream dependencies). SCIP has been
   designed so that it's also possible to generate spec-compliant symbols from

docs/getting-started.md

@@ -4,7 +4,7 @@ title: Getting started
 ---
 
 By following the instructions on this page, you should be able to generate a
-[SCIP](https://github.com/sourcegraph/scip) index of your Java codebase using
+[SCIP](https://github.com/scip-code/scip) index of your Java codebase using
 Gradle, Maven, or Bazel. See
 [Supported build tools](#supported-build-tools) for an overview of other build
 tools that we're planning to support in the future.

scip-java/src/main/resources/scip-java/scip_java.bzl

@@ -9,7 +9,7 @@ different contents.
 This aspect is needed for scip-java to inspect the structure of the Bazel build
 and register actions to index all java_library/java_test/java_binary targets.
 The result of running this aspect is that your bazel-bin/ directory will contain
-many *.scip (https://github.com/sourcegraph/scip) files.
+many *.scip (https://github.com/scip-code/scip) files.
 These files encode information about which symbols are referenced from which
 locations in your source code.
 

scip-javac/src/main/java/com/sourcegraph/scip_javac/GlobalSymbolsCache.java

@@ -117,7 +117,7 @@ private ScipSymbols.Descriptor scipDescriptor(Element sym) {
   }
 
   /**
-   * Computes the method "disambiguator" according to the SCIP spec.
+   * Computes the method "disambiguator" according to the SemanticDB spec.
    *
    * <p><quote> Concatenation of a left parenthesis ("("), a tag and a right parenthesis (")"). If
    * the definition is not overloaded, the tag is empty. If the definition is overloaded, the tag is
@@ -131,7 +131,8 @@ private ScipSymbols.Descriptor scipDescriptor(Element sym) {
    *
    * </quote>
    *
-   * <p><a href="https://scalameta.org/docs/scip/specification.html#symbol-2">Link to SCIP spec</a>.
+   * <p><a href="https://scalameta.org/docs/semanticdb/specification.html#symbol-2">Link to
+   * SemanticDB spec</a>.
    */
   private String methodDisambiguator(ExecutableElement sym) {
     Iterable<? extends Element> elements = sym.getEnclosingElement().getEnclosedElements();