Which dependency for compose devservices

[Postremus]

I try to use the compose devservices:
https://quarkus.io/guides/compose-dev-services

Which dependency is needed for it?

I see that the source code for the compose devservices is in e.g. inhttps://github.com/quarkusio/quarkus/blob/main/extensions/devservices/deployment/src/main/java/io/quarkus/devservices/deployment/compose/ComposeDevServicesProcessor.java

(And not a distinct quarkus-devservices-common)

So I tried to add as dependency:

        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-devservices</artifactId>
            <scope>test</scope>
        </dependency>

Which resulted in:

[ERROR] Caused by: java.lang.RuntimeException: The following errors were encountered while processing Quarkus application dependencies:
[ERROR] 1) Quarkus extension deployment artifact io.quarkus:quarkus-devservices-deployment:jar:3.33.2 does not appear to depend on the corresponding runtime artifact io.quarkus:quarkus-devservices:jar:3.33.2
[ERROR]   at io.quarkus.bootstrap.resolver.maven.ApplicationDependencyResolver$ExtensionDependency.collectDeploymentDeps(ApplicationDependencyResolver.java:1015)

(which is already tracked as #49026).

So my question is - how do i use the compose devservices, when I do not depend already on any other devservices?

[quarkus-bot[bot]]

/cc @geoand (devservices), @holly-cummins (devservices), @ozangunalp (devservices)

[holly-cummins]

The quarkus-devservices dependency is intended for other dev services to use, not end-user applications. But I think you're right that this leaves a gap, if you want compose but no other dev services! You could work around by adding another dependency that has a dev service but then disabling that specific service, but it's clearly a bit of a hack, and depending what service you choose, might cause startup errors. I suspect it didn't occur to us that someone might do an application without any database or messaging dependencies.

Can you raise an issue?

[Postremus]

Thank you, your suggested workaround works. :)

I opened #55258