-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Circular dependency in boringssl-static/pom.xml
#727
Labels
Comments
4 tasks
Looks like the Bazel issue was fixed in bazelbuild/rules_jvm_external@d2c7811 |
FWIW I have recently also encountered this in maven. For each platform we support I need to do this: <dependency>
<groupId>io.netty</groupId>
<artifactId>netty-tcnative-boringssl-static</artifactId>
<version>2.0.60.Final</version>
<classifier>osx-aarch_64</classifier>
<exclusions>
<exclusion>
<groupId>io.netty</groupId>
<artifactId>netty-tcnative-boringssl-static</artifactId>
</exclusion>
</exclusions>
</dependency> |
The same happens with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
boringssl-static/pom.xml
defines the dependencies that depend on themselves: https://github.com/netty/netty-tcnative/blob/netty-tcnative-parent-2.0.52.Final/boringssl-static/pom.xml#L731-L762I guess the original intention of this dependency is to pull all native libraries for all platforms by just depending on
netty-tcnative-boringssl
, but it prevents a user from pulling a native library for only one platform by depending on something likenetty-tcnative-boringssl:linux-x86_64
. It also is a circular dependency which is maybe not desirable:I didn't look into other
netty-tcnative-*
POMs, but we'll also have to fix them if they have the same circular dependency.The text was updated successfully, but these errors were encountered: