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
The issue I am seeing is that when I have dependencies in common that are transitive to things that depend on it, the subprojects cannot resolve the version of the project they depend on. I've attached a sample project that demonstrates the issue.
> Task :test-subproject:compileJava FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':test-subproject:compileJava'.
> Could not resolve all files for configuration ':test-subproject:compileClasspath'.
> Could not find co.elastic.apm:apm-agent-api:.
Required by:
project :test-subproject > project :test-common
The only workaround I was able to find was to add a dependency block in each subproject to map the version, but that kind of defeats the point of using the plugin...
We have a multi-project setup with a common module and various subprojects that rely on the common project:
The issue I am seeing is that when I have dependencies in common that are transitive to things that depend on it, the subprojects cannot resolve the version of the project they depend on. I've attached a sample project that demonstrates the issue.
The only workaround I was able to find was to add a dependency block in each subproject to map the version, but that kind of defeats the point of using the plugin...
SpringDep.zip
The text was updated successfully, but these errors were encountered: