launchdarkly · LaunchDarklyReleaseBot · May 4, 2022 · May 23, 2020 · May 23, 2020 · May 23, 2020
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -448,7 +448,7 @@ It is now possible to inject feature flags into the client from local JSON or YA
 ## [4.0.0] - 2018-05-10
 
 ### Changed:
-- To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option `inlineUsersInEvents`. For more details, see [Analytics Data Stream Reference](https://docs.launchdarkly.com/v2.0/docs/analytics-data-stream-reference).
+- To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option `inlineUsersInEvents`.
 - When sending analytics events, if there is a connection error or an HTTP 5xx response, the client will try to send the events again one more time after a one-second delay.
 - The `LdClient` class is now `final`.
 
@@ -509,7 +509,7 @@ _This release was broken and should not be used._
 
 ## [2.5.0] - 2018-01-08
 ## Added
-- Support for specifying [private user attributes](https://docs.launchdarkly.com/docs/private-user-attributes) in order to prevent user attributes from being sent in analytics events back to LaunchDarkly. See the `allAttributesPrivate` and `privateAttributeNames` methods on `LDConfig.Builder` as well as the `privateX` methods on `LDUser.Builder`.
+- Support for specifying [private user attributes](https://docs.launchdarkly.com/home/users/attributes#creating-private-user-attributes) in order to prevent user attributes from being sent in analytics events back to LaunchDarkly. See the `allAttributesPrivate` and `privateAttributeNames` methods on `LDConfig.Builder` as well as the `privateX` methods on `LDUser.Builder`.
 
 ## [2.4.0] - 2017-12-20
 ## Changed

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
 # Contributing to the LaunchDarkly Server-side SDK for Java
 
-LaunchDarkly has published an [SDK contributor's guide](https://docs.launchdarkly.com/docs/sdk-contributors-guide) that provides a detailed explanation of how our SDKs work. See below for additional information on how to contribute to this SDK.
+LaunchDarkly has published an [SDK contributor's guide](https://docs.launchdarkly.com/sdk/concepts/contributors-guide) that provides a detailed explanation of how our SDKs work. See below for additional information on how to contribute to this SDK.
 
 ## Submitting bug reports and feature requests
 

diff --git a/README.md b/README.md
@@ -5,7 +5,7 @@
 
 ## LaunchDarkly overview
 
-[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/docs/getting-started) using LaunchDarkly today!
+[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/home/getting-started) using LaunchDarkly today!
 
 [![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)
 
@@ -17,13 +17,13 @@ This version of the LaunchDarkly SDK works with Java 8 and above.
 
 Three variants of the SDK jar are published to Maven:
 
-* The default uberjar - this is accessible as `com.launchdarkly:launchdarkly-java-server-sdk:jar` and is the dependency used in the "[Getting started](https://docs.launchdarkly.com/docs/java-sdk-reference#section-getting-started)" section of the SDK reference guide as well as in the [`hello-java`](https://github.com/launchdarkly/hello-java) sample app. This variant contains the SDK classes, and all of the SDK's dependencies except for SLF4J, which must be provided by the host application. The bundled dependencies have shaded package names (and are not exported in OSGi), so they will not interfere with any other versions of the same packages.
+* The default uberjar - this is accessible as `com.launchdarkly:launchdarkly-java-server-sdk:jar` and is the dependency used in the "[Getting started](https://docs.launchdarkly.com/sdk/server-side/java#getting-started)" section of the SDK reference guide as well as in the [`hello-java`](https://github.com/launchdarkly/hello-java) sample app. This variant contains the SDK classes, and all of the SDK's dependencies except for SLF4J, which must be provided by the host application. The bundled dependencies have shaded package names (and are not exported in OSGi), so they will not interfere with any other versions of the same packages.
 * The extended uberjar - add `<classifier>all</classifier>` in Maven, or `:all` in Gradle. This is the same as the default uberjar except that SLF4J is also bundled, without shading (and is exported in OSGi).
 * The "thin" jar - add `<classifier>thin</classifier>` in Maven, or `:thin` in Gradle. This contains _only_ the SDK classes.
 
 ## Getting started
 
-Refer to the [SDK reference guide](https://docs.launchdarkly.com/docs/java-sdk-reference#section-getting-started) for instructions on getting started with using the SDK.
+Refer to the [SDK reference guide](https://docs.launchdarkly.com/sdk/server-side/java#getting-started) for instructions on getting started with using the SDK.
 
 ## Logging
 
@@ -62,7 +62,7 @@ We encourage pull requests and other contributions from the community. Check out
  * Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
  * Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
  * Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.
-* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Check out [our documentation](https://docs.launchdarkly.com/docs) for a complete list.
+* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Read [our documentation](https://docs.launchdarkly.com/sdk) for a complete list.
 * Explore LaunchDarkly
  * [launchdarkly.com](https://www.launchdarkly.com/ "LaunchDarkly Main Website") for more information
  * [docs.launchdarkly.com](https://docs.launchdarkly.com/ "LaunchDarkly Documentation") for our documentation and SDK reference guides

diff --git a/src/main/java/com/launchdarkly/sdk/server/Components.java b/src/main/java/com/launchdarkly/sdk/server/Components.java
@@ -74,7 +74,7 @@ public static DataStoreFactory inMemoryDataStore() {
  * See {@link PersistentDataStoreBuilder} for more on how this method is used.
  * <p>
  * For more information on the available persistent data store implementations, see the reference
- * guide on <a href="https://docs.launchdarkly.com/sdk/concepts/feature-store">Using a persistent feature store</a>.
+ * guide on <a href="https://docs.launchdarkly.com/sdk/concepts/data-stores">Using a persistent feature store</a>.
  * 
  * @param storeFactory the factory/builder for the specific kind of persistent data store
  * @return a {@link PersistentDataStoreBuilder}
@@ -197,7 +197,7 @@ static PollingDataSourceBuilderImpl pollingDataSourceInternal() {
  * <p>
  * Passing this to {@link LDConfig.Builder#dataSource(DataSourceFactory)} causes the SDK
  * not to retrieve feature flag data from LaunchDarkly, regardless of any other configuration.
- * This is normally done if you are using the <a href="https://docs.launchdarkly.com/docs/the-relay-proxy">Relay Proxy</a>
+ * This is normally done if you are using the <a href="https://docs.launchdarkly.com/home/relay-proxy">Relay Proxy</a>
  * in "daemon mode", where an external process-- the Relay Proxy-- connects to LaunchDarkly and populates
  * a persistent data store with the feature flag data. The data store could also be populated by
  * another process that is running the LaunchDarkly SDK. If there is no external process updating

diff --git a/src/main/java/com/launchdarkly/sdk/server/FeatureFlagsState.java b/src/main/java/com/launchdarkly/sdk/server/FeatureFlagsState.java
@@ -23,7 +23,7 @@
  * calling {@link LDClientInterface#allFlagsState(com.launchdarkly.sdk.LDUser, FlagsStateOption...)}.
  * <p>
  * LaunchDarkly defines a standard JSON encoding for this object, suitable for
- * <a href="https://docs.launchdarkly.com/sdk/client-side/javascript#bootstrapping">bootstrapping</a>
+ * <a href="https://docs.launchdarkly.com/sdk/features/bootstrapping#javascript">bootstrapping</a>
  * the LaunchDarkly JavaScript browser SDK. You can convert it to JSON in any of these ways:
  * <ol>
  * <li> With {@link com.launchdarkly.sdk.json.JsonSerialization}.

diff --git a/src/main/java/com/launchdarkly/sdk/server/integrations/EventProcessorBuilder.java b/src/main/java/com/launchdarkly/sdk/server/integrations/EventProcessorBuilder.java
@@ -92,7 +92,7 @@ public EventProcessorBuilder allAttributesPrivate(boolean allAttributesPrivate)
  * <p>
  * You will only need to change this value in the following cases:
  * <ul>
- * <li> You are using the <a href="https://docs.launchdarkly.com/docs/the-relay-proxy">Relay Proxy</a> with
+ * <li> You are using the <a href="https://docs.launchdarkly.com/home/relay-proxy">Relay Proxy</a> with
  * event forwarding enabled. Set {@code streamUri} to the base URI of the Relay Proxy instance.
  * <li> You are connecting to a test server or a nonstandard endpoint for the LaunchDarkly service.
  * </ul>

diff --git a/src/main/java/com/launchdarkly/sdk/server/integrations/PollingDataSourceBuilder.java b/src/main/java/com/launchdarkly/sdk/server/integrations/PollingDataSourceBuilder.java
@@ -40,7 +40,7 @@ public abstract class PollingDataSourceBuilder implements DataSourceFactory {
  * <p>
  * You will only need to change this value in the following cases:
  * <ul>
- * <li> You are using the <a href="https://docs.launchdarkly.com/docs/the-relay-proxy">Relay Proxy</a>. Set
+ * <li> You are using the <a href="https://docs.launchdarkly.com/home/relay-proxy">Relay Proxy</a>. Set
  * {@code streamUri} to the base URI of the Relay Proxy instance.
  * <li> You are connecting to a test server or anything else other than the standard LaunchDarkly service.
  * </ul>

diff --git a/src/main/java/com/launchdarkly/sdk/server/integrations/StreamingDataSourceBuilder.java b/src/main/java/com/launchdarkly/sdk/server/integrations/StreamingDataSourceBuilder.java
@@ -36,7 +36,7 @@ public abstract class StreamingDataSourceBuilder implements DataSourceFactory {
  * <p>
  * You will only need to change this value in the following cases:
  * <ul>
- * <li> You are using the <a href="https://docs.launchdarkly.com/docs/the-relay-proxy">Relay Proxy</a>. Set
+ * <li> You are using the <a href="https://docs.launchdarkly.com/home/relay-proxy">Relay Proxy</a>. Set
  * {@code baseUri} to the base URI of the Relay Proxy instance.
  * <li> You are connecting to a test server or a nonstandard endpoint for the LaunchDarkly service.
  * </ul>