-
Notifications
You must be signed in to change notification settings - Fork 316
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
Teku Maven artifacts issues when including as dependency #7444
Comments
The fix should be something like c91265d I tested it against a local maven repo and I now get:
@Nashatyrev might be good enough? |
sorry @courtneyeh I was curious about this and I ended up spending a bit on it so I wanted to share what I did. on my local teku i run
and on a test project i used:
|
using version |
Thanks @tbenr is this okay to close now? |
@courtneyeh I did additional checks and seems to work, at least locally. |
Description
When using different versions of
io.spring.dependency-management
gradle plugin including any Teku module artifact as a maven dependency to a gradle build the following error may occur:1.1.0
: no errors1.1.1
: build fails with the following error (plugin issue here)1.1.3
: build succeeds bu the the following error(s) are printed:The above errors indicate another problem: all dependencies of
test-fixture
scope are also picked up when only module runtime dependencies are required. Here is some more insights: https://stackoverflow.com/questions/69877418/why-does-every-pom-file-published-by-gradle-has-a-self-referential-dependencySteps to Reproduce (Bug)
run
gradle build
for the followingbuild.gradle
Expected behavior:
Successful build
Only required artifacts are imported
Actual behavior:
Build fails with the errors described above (depending on the plugin version)
Frequency: Always
Versions (Add all that apply)
Related issues:
Libp2p PR: libp2p/jvm-libp2p#306
The text was updated successfully, but these errors were encountered: