You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run into a problem where I got two conflicting zio-test version in my project. And root cause was that
"dev.zio" %% "zio-aws-sqs" requiring the zio-mock as a non test dependency: libraryDependencies += "dev.zio" %% "zio-mock" % zioMockLibraryVersion.value,
Could this be replaced with: libraryDependencies += "dev.zio" %% "zio-mock" % zioMockLibraryVersion.value % Test,
The text was updated successfully, but these errors were encountered:
It is not using it for testing, it provides zio-mock definitions for the generated services so it cannot be a test dependency.
I believe the right thing to do would be to expose the mocks in a separate artifact (like zio-aws-s3 without depending on zio-mock and zio-aws-s3-mocks with the generated mocks).
Originally I did not do this because zio-aws is already publishing about 1000 artifacts in one run (~350 aws services, 3 scala versions) and this would double that.
I run into a problem where I got two conflicting zio-test version in my project. And root cause was that
"dev.zio" %% "zio-aws-sqs" requiring the zio-mock as a non test dependency:
libraryDependencies += "dev.zio" %% "zio-mock" % zioMockLibraryVersion.value,
Could this be replaced with:
libraryDependencies += "dev.zio" %% "zio-mock" % zioMockLibraryVersion.value % Test,
The text was updated successfully, but these errors were encountered: