transitive-dependency

What is wrong with a transitive dependency?

阅读更多关于 What is wrong with a transitive dependency?

问题 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

Maven - transitive dependencies with different versions

阅读更多关于 Maven - transitive dependencies with different versions

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? 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 dependency tree, until Maven 2.0.8 it was not defined which one would win, but since Maven 2.0.9 it's the order in

Gradle multiproject optional subproject's transitive dependency should be resolved to an existing subproject

阅读更多关于 Gradle multiproject optional subproject's transitive dependency should be resolved to an existing subproject

问题 suppose the following project. the master project is a multi-project, however every part of the larger project can be developed individually or mixed in: /master/build.gradle /m1/build.gradle /m2/build.gradle /m3/build.gradle suppose m3 uses m2 and m2 uses m1 ( m1 <- m2 <- m3 ) the presence of m2 is optional a multi-project with the following layout also reasonable /master/build.gradle /m1/build.gradle /m3/build.gradle but in this case m2 would be pulled in from the artifact repository which

Gradle, How To Disable All Transitive Dependencies

阅读更多关于 Gradle, How To Disable All Transitive Dependencies

问题 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 } 回答1: I ended up using: configurations.all {

Transitive references in .Net Core 1.1

阅读更多关于 Transitive references in .Net Core 1.1

While developing a sample web app in .NET Core 1.1 and Visual Studio 2017 RC, I realized the following: As you can see: ClassLibrary3 has a reference to ClassLibrary2, and ClassLibrary2 has a reference to ClassLibrary1 I wrote a simple method in class Class3 of ClassLibrary3 project, and the Intellisense allowed me to use Class1 just writing the name of the class, I mean, without doing an explicit reference to ClassLibrary1 project. Am I missing some point here? I don't want somebody simply comes and overlooks ClassLibrary2. Thanks. Transitive project-to-project references are a new feature of

Transitive references in .Net Core 1.1

阅读更多关于 Transitive references in .Net Core 1.1

问题 While developing a sample web app in .NET Core 1.1 and Visual Studio 2017 RC, I realized the following: As you can see: ClassLibrary3 has a reference to ClassLibrary2, and ClassLibrary2 has a reference to ClassLibrary1 I wrote a simple method in class Class3 of ClassLibrary3 project, and the Intellisense allowed me to use Class1 just writing the name of the class, I mean, without doing an explicit reference to ClassLibrary1 project. Am I missing some point here? I don\'t want somebody simply

What's the difference between implementation and compile in Gradle?

阅读更多关于 What's the difference between implementation and compile in Gradle?

问题 After updating to Android Studio 3.0 and creating a new project, I noticed that in build.gradle there is a new way to add new dependencies instead of compile there is implementation and instead of testCompile there is testImplementation . Example: implementation \'com.android.support:appcompat-v7:25.0.0\' testImplementation \'junit:junit:4.12\' instead of compile \'com.android.support:appcompat-v7:25.0.0\' testCompile \'junit:junit:4.12\' What\'s the difference between them and what should I

What is wrong with a transitive dependency?

Maven - transitive dependencies with different versions

Gradle multiproject optional subproject's transitive dependency should be resolved to an existing subproject

Gradle, How To Disable All Transitive Dependencies

Transitive references in .Net Core 1.1

Transitive references in .Net Core 1.1

What&#39;s the difference between implementation and compile in Gradle?

What's the difference between implementation and compile in Gradle?