chore(deps): update dependency java to v25 - autoclosed

[renovate]

This PR contains the following updates:

Package	Update	Change
java	major	21.0.9+10.0.LTS -> 25.0.1+8.0.LTS

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[trask]

@zeitlinger is this expected for it to fail on Java 25?

[zeitlinger]

@zeitlinger is this expected for it to fail on Java 25?

The java version in the dockerfile must be updated first - should we create a rule to bundle them in renovate?

[zeitlinger]

The java version in the dockerfile must be updated first - should we create a rule to bundle them in renovate?

docker file updates are disabled

opentelemetry-java-examples/.github/renovate.json5

Line 38 in dc7a404

"matchPackageNames": ["eclipse-temurin"],

I created #910 to remove the pin

@trask I can't see why they were disabled - can you remember?

[trask]

@zeitlinger is this expected for it to fail on Java 25?

The java version in the dockerfile must be updated first - should we create a rule to bundle them in renovate?

can you explain the issue a bit more? thanks

@trask I can't see why they were disabled - can you remember?

yeah, we were intentionally running examples on earlier Java versions, but we can definitely revisit this (as long as we still compile the bytecode to earlier version to make sure users can copy-paste the examples into apps still running on earlier Java versions)

[zeitlinger]

The java version in the dockerfile must be updated first - should we create a rule to bundle them in renovate?

can you explain the issue a bit more? thanks

I think we can't tell renovate to update one dependency before or together with another - because one of from docker and the other from mise

yeah, we were intentionally running examples on earlier Java versions, but we can definitely revisit this (as long as we still compile the bytecode to earlier version to make sure users can copy-paste the examples into apps still running on earlier Java versions)

created #915

[trask]

sorry, what I was trying to ask (poorly) is what does oats use Java for (wondering why needs to be aligned)?

[zeitlinger]

sorry, what I was trying to ask (poorly) is what does oats use Java for (wondering why needs to be aligned)?

this is the workflow:

• app is build using the java version from mise in

  opentelemetry-java-examples/.mise/tasks/oats-tests.sh

  Line 7 in 524a739

  ../gradlew clean assemble

• OATs invokes docker to run the app:

  opentelemetry-java-examples/logging-k8s-stdout-otlp-json/Dockerfile

  Line 1 in d8b3a7b

  FROM eclipse-temurin:21.0.9_10-jre@sha256:4332b7939ba5b7fabde48f4da21ebe45a4f8943d5b3319720c321ac577e65fb1

[trask]

can we limit the mise action to just running oats? and using our normal workflow for running gradle?

[zeitlinger]

can we limit the mise action to just running oats? and using our normal workflow for running gradle?

Yes, but that would mean that you can't locally run mise run oats-tests as a one-stop command to build the app and run the test.

[trask]

yeah, I would prefer not to use mise as a replacement for running gradle at this point

[zeitlinger]

yeah, I would prefer not to use mise as a replacement for running gradle at this point

got it - created #922, which should auto-close this PR

[zeitlinger]

yeah, I would prefer not to use mise as a replacement for running gradle at this point

got it - created #922, which should auto-close this PR

once #923 is merged