We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have a micronaut library that has
api("io.micronaut.redis:micronaut-redis-lettuce")
Therefore, I do NOT specify it explicitly like below in my service using the library
implementation("io.micronaut.redis:micronaut-redis-lettuce")
When I look at my IntelliJ extern libs I see redis
I then expect micronaut test resources to start my redis container but it does not
I AM including Kakfa in my repo since the library does not implementation("io.micronaut.kafka:micronaut-kafka")
implementation("io.micronaut.kafka:micronaut-kafka")
[test-resources-service] 16:49:32.313 [ForkJoinPool.commonPool-worker-7] INFO i.m.t.e.TestResourcesResolverLoader - Loaded 2 test resources resolvers: io.micronaut.testresources.kafka.KafkaTestResourceProvider, io.micronaut.testresources.testcontainers.GenericTestContainerProvider
implementation
No response
4.2.2
The text was updated successfully, but these errors were encountered:
melix
No branches or pull requests
Expected Behavior
I have a micronaut library that has
api("io.micronaut.redis:micronaut-redis-lettuce")
Therefore, I do NOT specify it explicitly like below in my service using the library
implementation("io.micronaut.redis:micronaut-redis-lettuce")
When I look at my IntelliJ extern libs I see redis
Expected
I then expect micronaut test resources to start my redis container but it does not
I AM including Kakfa in my repo since the library does not
implementation("io.micronaut.kafka:micronaut-kafka")
Actual Behaviour
Steps To Reproduce
api("io.micronaut.redis:micronaut-redis-lettuce")
implementation
Environment Information
Example Application
No response
Version
4.2.2
The text was updated successfully, but these errors were encountered: