transitive-dependency

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 not accessible) ? In other words is there a way where I can have Project B and X each using their own

I add a dependency(let's name it as A) to ivy.xml which has a pom file in maven central. Ivy uses ibiblio for resolving the maven dependencies. The dependency(A) which is added to ivy.xml has a transitive dependency(B). So far so good till here. The dependency(C) of transitive dependency(B) can not be resolved by ivy. I defined A in ivy.xml like this: <dependency org="Z" name="A" rev="0.6-SNAPSHOT" conf="*->default"/> In pom file of B, C is defined both in compile and test scopes like below: <dependency> <groupId>X</groupId> <artifactId>C</artifactId> </dependency> <dependency> <groupId>X<

I have two projects - A and B, where A is dependent on B. I package B as jar and deploy it on a maven server (artifactory), and then include that jar as a normal dependency on project A in pom file. jar file of B shows up in the Maven Dependencies of project A, but dependencies of project B are not shown in dependency hierarchy. It is causing class not found exception for dependencies of B. However, my project A and B and in same eclipse workspace. When I open project B, project A starts referencing the project B from the workspace instead of remote repository and everything works well. This

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 with self-chosen group/artifact/version and a " <scope>system</scope><systemPath>${project.basedir}/lib

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? When is one version used over another version ? If you declare the Used undeclared dependency with a

I have some transitive dependencies in my database design. I have been told by my superiors that these can cause bugs. I am finding it difficult to find resources that will tell me how having these dependencies will cause bugs. What kind of problems will they cause? I am not disputing the fact, just eager to learn what kind of problems they can cause. Edit for more details: From wikipedia : Transitive dependency A transitive dependency is an indirect functional dependency, one in which X→Z only by virtue of X→Y and Y→Z. I'll explain by an example: ----------------------------------------------

Many of my jars have conflicting transitive dependencies (multiple spring versions). I would like to avoid inherited version conflicts by managing all of my dependencies explicitly, is it possible to disable all transitive dependencies in Gradle? I know I can add transitive = false to each of my dependencies, but I am hoping there is a simpler way. compile(group: 'org.springframework', name: 'spring', version: '2.5.2') { transitive = false } I ended up using: configurations.all { transitive = false } If you want to have just one configuration block for all configurations you can use spread-dot