-
Notifications
You must be signed in to change notification settings - Fork 850
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
Unable to use composite build #3626
Comments
I feel as if tweaking the names how we do it isn't so weird. Should we file an issue in gradle repo? Though either way the workaround for the old Gradle issue could still be a blocker... |
I mean, changing artifact name just for publishing does seem weird to me :D |
This is more of an issue of opentelemetry-java, right? Since it isn't friendly to gradle's composite build feature with its many limitations: https://docs.gradle.org/current/userguide/composite_builds.html#current_limitations_and_future_work and https://docs.gradle.org/current/userguide/composite_builds.html#included_build_substitution_limitations |
@Oberon00 we have absolutely the same issue in this very repo, e.g. when trying to build |
I'm playing around with building the examples in otel-java with the main project as included build: open-telemetry/opentelemetry-java#3603 |
PR open-telemetry/opentelemetry-java#3653 was now merged and generates code snippets with the required gradle dependency substitutions for the included build. |
Currently it is impossible to include this repo into a composite build from another project. The reason is that this project's modules declare e.g. the following name in its metadata:
io.opentelemetry.javaagent:javaagent:1.4.0-SNAPSHOT
. But during publishing we addopentelemetry-
prefix to artifact name and so a dependant project will declare its dependency uponio.opentelemetry.javaagent:opentelemetry-javaagent
.Thus during composite build gradle tries to find
opentelemetry-javaagent
artifact from this project and fails.The text was updated successfully, but these errors were encountered: