Refactor java instrumentation

.gitmodules

@@ -31,4 +31,4 @@
 [submodule "content-modules/opentelemetry-java-examples"]
 	path = content-modules/opentelemetry-java-examples
 	url = https://github.com/open-telemetry/opentelemetry-java-examples.git
-	javaexamples-pin = 8fe9a11
+	javaexamples-pin = 0f736ec

.htmltest.yml

@@ -10,6 +10,8 @@ IgnoreDirs:
   - ^blog/(\d+/)?page/\d+
   # TODO drop after https://github.com/open-telemetry/opentelemetry.io/issues/5267 is fixed:
   - zh/docs/contributing/pr-checks
+  # TODO drop after https://github.com/open-telemetry/opentelemetry.io/issues/5423 is fixed:
+  - (ja|pt)/docs/concepts/instrumentation/libraries/
 IgnoreInternalURLs: # list of paths
 IgnoreURLs: # list of regexs of paths or URLs to be ignored
   - ^/api$

content/en/blog/2023/spring-native/index.md

@@ -37,11 +37,11 @@ Boot 3) out of the box:
 ```
 
 To get even more visibility, the Starter can be combined with
-[instrumentation libraries](/docs/languages/java/libraries/). For this purpose,
-the OpenTelemetry Java contributors have improved the JDBC (database) libraries
-and logging instrumentation libraries. For example, for the Logback logging
-library, they have added GraalVM configuration to make the library work in
-native mode[^1].
+[instrumentation libraries](/docs/languages/java/instrumentation/). For this
+purpose, the OpenTelemetry Java contributors have improved the JDBC (database)
+libraries and logging instrumentation libraries. For example, for the Logback
+logging library, they have added GraalVM configuration to make the library work
+in native mode[^1].
 
 Furthermore, they have worked to reduce the configuration to set up the logging
 and database instrumentation with the Starter. For example, if your application

content/en/docs/collector/deployment/agent.md

@@ -129,7 +129,7 @@ Cons:
 [instrumentation]: /docs/languages/
 [otlp]: /docs/specs/otel/protocol/
 [collector]: /docs/collector/
-[instrument-java-metrics]: /docs/languages/java/instrumentation/#metrics
+[instrument-java-metrics]: /docs/languages/java/api-components/#meterprovider
 [otlp-exporter]: /docs/specs/otel/protocol/exporter/
 [java-otlp-example]:
   https://github.com/open-telemetry/opentelemetry-java-docs/tree/main/otlp

content/en/docs/concepts/instrumentation/libraries.md

@@ -265,7 +265,7 @@ After you create a span, pass new trace context to the application code
 (callback or handler), by making the span active; if possible, do this
 explicitly. The following Java example shows how to add trace context and
 activate a span. See the
-[Context extraction in Java](/docs/languages/java/instrumentation/#context-propagation),
+[Context extraction in Java](/docs/languages/java/api-components/#contextpropagators),
 for more examples.
 
 ```java
@@ -289,9 +289,7 @@ try (Scope unused = span.makeCurrent()) {
 ```
 
 In the case of a messaging system, you might receive more than one message at
-once. Received messages become
-[links](/docs/languages/java/instrumentation/#create-spans-with-links) on the
-span you create. Refer to
+once. Received messages become links on the span you create. Refer to
 [messaging conventions](/docs/specs/semconv/messaging/messaging-spans/) for
 details.