Use latest Javadoc everywhere

docs/androidx_test.md

@@ -14,7 +14,7 @@ test. Furthermore it will make your tests more portable and compatible with our
 ### TestRunner
 
 It is now possible to use the AndroidX test runner in Robolectric tests. If you require a custom test runner currently,
-please check out the new [configuration and plugin API](http://robolectric.org/javadoc/4.2/org/robolectric/pluginapi/package-summary.html)
+please check out the new [configuration and plugin API](javadoc/latest/org/robolectric/pluginapi/package-summary.html)
 and let us know if there are any extension points missing that you require.
 
 **Robolectric**

docs/configuring.md

@@ -9,7 +9,7 @@ Several aspects of Robolectric's behavior can be configured at runtime, using `r
 
 ### `@Config` Annotation
 
-To configure Robolectric for a single test class or method, use the <a href="/javadoc/latest/org/robolectric/annotation/Config.html">`@Config`</a> annotation. The annotation can be applied to classes and methods; values specified at the method level will override values specified at the class level.
+To configure Robolectric for a single test class or method, use the [`@Config`](javadoc/latest/org/robolectric/annotation/Config.html) annotation. The annotation can be applied to classes and methods; values specified at the method level will override values specified at the class level.
 
 Base classes are also searched for annotations, so if you find yourself specifying the same values on a large number of tests, you can create a base class and move your `@Config` annotation to that class.
 

docs/contributing.md

@@ -54,7 +54,7 @@ Robolectric uses javadoc to document API's behavior. There are special rules for
 * All visible non-`@Implementation` methods SHOULD have descriptive Javadoc.
 * Don't write javadoc comments like "Shadow for (whatever).". The javadoc will appear in a section clearly related to testing, so make it make sense in context.
 
-Robolectric will release javadoc at robolectric.org after every main version released. For example, Robolectric's 4.7 javadoc is released at http://robolectric.org/javadoc/4.7/.
+Robolectric will release javadoc at robolectric.org after every main version released. For example, Robolectric's {{ robolectric.version.current }} javadoc is released at {{ site_url }}javadoc/{{ robolectric.version.current }}/.
 
 ### Deprecations and Backwards Compatibility
 

docs/device-configuration.md

@@ -79,7 +79,7 @@ public void testOrientationChange() {
 
 The string parameter to `setQualifiers()` has the same rules as `Config.qualifiers`.
 
-Note that `RuntimeEnvironment.setQualifiers()` updates the system and application resources with the new configuration, but does not trigger any action on extant activities or other components. [`ActivityController.configurationChange()`](http://robolectric.org/javadoc/latest/org/robolectric/android/controller/ActivityController.html#configurationChange-android.content.res.Configuration-) can be used to simulate the sequence of events that take place on a device when its configuration changes.
+Note that `RuntimeEnvironment.setQualifiers()` updates the system and application resources with the new configuration, but does not trigger any action on extant activities or other components. [`ActivityController.configurationChange()`](javadoc/latest/org/robolectric/android/controller/ActivityController.html#configurationChange-android.content.res.Configuration-) can be used to simulate the sequence of events that take place on a device when its configuration changes.
 
 If the activity is configured to handle the configuration changes, `ActivityController.configurationChange()` will call the activity’s `onConfigurationChanged()` method. If not, `ActivityController` destroys and recreates the activity.