transitive-dependency

问题 I am migrating an old style MsBuild csproj project to using PackageReference format and have run into a problem with transitive dependencies. Consider the following Project A reference NuGet package B and C, each containing one single assembly using PackageReference. On Build Project A uses IL merge to incorporate B as public symbols in the A assembly and C as internalized symbols. Project D have a project reference to A. The transitive dependencies case D to reference A, B and C. When

问题 I am working on an existing Python 3 code-base that provides a setup.py so the code is installed as a Python library. I am trying to get this internal library installed with its own dependencies (the usual data science ones e.g. pandas , pyodbc , sqlalchemy etc). I would like to have this internal library to deal with these dependencies and assume that if that library is installed, then all the transitive dependencies are assumed to be installed . I also would like to have the Anaconda (

问题 I just finally got used to not having any Used undeclared or Unused declared dependencies in my projects. Although it is very hard to track Unused declared runtime/test dependencies that are listed in dependency:analyze... One just must write comments to them in pom.xml or otherwise manage them to know that they are needed for testing or runtime. But the way of resolving version conflict is still unclear to me. Regarding transitive dependencies. How does the nearest-wins strategy work exactly

问题 It seems, that in my Eclipse Oxygen 3 transitive dependencies are not resolved in Plugin-Projects. Consider the following Project with A depending solely on B, and B depending on C: While running A in JDK 1.8 turns out fine (as expected), in JDK 9 I get the well known Exception in thread "main" java.lang.NoClassDefFoundError: c/C at b.B.<init>(B.java:9) at a.A.main(A.java:8) Caused by: java.lang.ClassNotFoundException: c.C at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass

问题 What is the best practice in the .NET world to manage transitive dependencies that cause version conflict ? In details : Project A Depends on Project B which in turn depends on library C also Project A also depends on Project X which depends on a DIFFERENT and (potentially) incompatible version of library C. A->B->Cv1.0 & A->X->Cv2.0 where Cv1.0 <> Cv2.0 Is there a way to make this work ? Can it be done WITHOUT using the GAC ? Can it be done even if B and X are in binary format only (source

问题 Let's assume my application needs foo.jar and bar.jar foo.jar needs version 1.0 of c.jar bar.jar needs version 2.0 of c.jar How does Maven resolve this conflict? Which version of c.jar will be used? 回答1: It depends on the order of declaration in your effective POM. If foo.jar shows up first you will get version 1.0 of c.jar . If on the other hand bar.jar is declared first it will be version 2.0 of c.jar . Relevant documentation: ...two dependency versions are at the same depth in the

问题 I have the following scenario: mylib is a library (for which I have the sources, so I'd like to put them into a Maven project mylib:mylib for example). This library has a jar dependency for which I only have the jar, and it is not to be found in the Maven repository (and I do NOT want to install it there either). To make it compile, something like this would work: add the jar file to the mylib project in a "lib" folder, e.g. "lib/thirdpartylib.jar" and in mylib's pom.xml, add a dependency

问题 I am working on a project that has a dependency of JUnit 4.11 and a transitive dependency of JMock 2.6.0-RC2 who in turn has a dependency of JUnit-dep 4.4 . This transitive dependency of JUnit-dep is overriding the setting in my local pom for JUnit . By overriding, I mean that when I call a JUnit method, it calls the one from v4.4 as opposed to v4.11. Adding exclusions for JMock and for JUnit-dep had no effect on my resolved dependencies. Note: JUnit and JUnit-dep have separate artifactId s,

问题 Basically, my web service must be deployable as a single OSGi jar bundle. Therefore: The bundle must contain all compile and runtime maven dependencies. It must also contain all non-optional dependencies that depend on those dependencies (i.e., the transitive dependencies). I'm attempting to use the maven-bundle-plugin to accomplish this. I've used Embed-Dependency to get all my compile and runtime dependencies in the bundle, and I've used Embed-Transitive to embed all the transitive

问题 Suppose we are working on mortgage sub-module, and we are directly using the Google Guava classes in module code, but the dependcy for the guava is defined in other sub-module under the same parent and we have access to Guava classes only by transitive dependency on "investment" module: banking-system (parent pom.xml) | |-- investment (pom.xml defines <dependency>guava</dependency>) | |-- mortgage (pom.xml defiens <dependency>investment</dependency>) Should we still put a <dependency> to