Updating quarkus 3.2 -> 3.8 fails with opentracing dependency

[mocenas]

Describe the bug

Using quarkus CLI 3.12.3. I create project on stream 3.2 (version 3.2.12.Final), add dependency:

<dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-smallrye-opentracing</artifactId>
      <version>3.12.3</version>
</dependency>

and start CLI update to stream 3.8 (to 3.8.5). Update fails on opentracing dependency not having the version set. After update, pom.xml contains dependency:

<dependency>
   <groupId>io.quarkiverse.opentracing</groupId>
   <artifactId>quarkus-smallrye-opentracing</artifactId>
</dependency>

which should have the version set as well, according to https://github.com/quarkusio/quarkus-updates/blob/main/recipes/src/main/resources/quarkus-updates/core/3.6.yaml

If I update to current main (3.12.3) it works fine, but updating to 3.8 fails.
Also doing the update for quarkus CLI v. 3.8.5 makes the update return success, but no changes are actually made.

I'm attaching log from update command
update.log

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

1. Create an app - quarkus create app app --stream=3.2 -Dquarkus.analytics.disabled=true
2. Add dependency to pom.xml:

    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-smallrye-opentracing</artifactId>
      <version>3.12.3</version>
    </dependency>

3. Exec quarkus update quarkus update --stream=3.8

Output of uname -a or ver

No response

Output of java -version

17

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

quarkus CLI 3.12.3

Additional information

No response

[quarkus-bot]

/cc @brunobat (tracing), @radcortez (tracing)

[rsvoboda]

/CC @gsmet @aloubyansky

[brunobat]

Opentracing is not supported anymore.

[rsvoboda]

Update tool should at least point to io.quarkiverse.opentracing:quarkus-smallrye-opentracing:1.0.0

Is it possible to print a warning about usage of deprecated extension?

[michalvavrik]

Update tool should at least point to io.quarkiverse.opentracing:quarkus-smallrye-opentracing:1.0.0

It seems SR OT is on Quarkus 3.6 https://github.com/quarkiverse/quarkus-smallrye-opentracing/blob/main/pom.xml#L30. It doesn't seem like a good idea to use it with 3.8.

[brunobat]

@michalvavrik @rsvoboda The extension is not supported or maintained:

[michalvavrik]

got it, let's close this; thanks

[rsvoboda]

OK, we do not support SR OT, shouldn't update tool fail in that case so the user adjusts the app?

The app was build-able and runnable, but after running the tool it's not buildable anymore.

I would expect that the update tool would fail with a message that SR OT is no longer maintained and the app needs some rework to be supported with the latest Quarkus.