Skip to content
New issue

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

Subproject not able to resolve versions of common module #308

Closed
LethiferousMoose opened this issue Sep 8, 2021 · 1 comment
Closed

Comments

@LethiferousMoose
Copy link

LethiferousMoose commented Sep 8, 2021

We have a multi-project setup with a common module and various subprojects that rely on the common project:

project
│   build.gradle
│   settings.gradle  
│
└───common
│   │   src
│   │   build.gradle
│   │
└───subproject
     │   src
     │   build.gradle

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...

SpringDep.zip

@wilkinsona
Copy link
Contributor

Duplicate of #94.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants