dependency-management

I'll explain the question with my real situation. I use logback 1.0.1 for logging, and it includes SLF4J 1.6.4 as a dependency. I also use the SLF4J API bridges for legacy logging API's (java.util.logging, log4j and commons-logging), which are not explicit dependencies. These must also (preferrably) be version 1.6.4. Trying to make my pom.xml as neat and error-free as possible, I'd like to enforce that these API bridges be the same version as SLF4J. The only way I know is to manually define them as dependencies in my pom.xml using version 1.6.4. If I ever update logback and the required SLF4J

I tried to add a Maven dependency to my project, which uses Gradle, by adding these lines to the build.gradle file in Android Studio: repositories { mavenCentral() } dependencies { compile files('libs/android-support-v4.jar') compile 'org.roboguice:roboguice:2.0' } The project seems to compile well, but there's no way to reference Roboguice classes inside my project's code. I feel like I'm missing something, namely, how does Gradle download the dependency and where will it store it? How should I fix my project? Using the command line, in the root of your project, run : ./gradlew clean && .

I've written an sbt plugin called sbt-jumi which implements sbt integration for Jumi . Right now the sbt-jumi plugin depends on the current Jumi release. Here is the relevant line from the plugin's build.sbt : libraryDependencies += "fi.jumi" % "jumi-launcher" % "0.5.376" And a user of the plugin would add this to his project/plugins.sbt file: addSbtPlugin("fi.jumi.sbt" % "sbt-jumi" % "0.1.0") Now let's say that Jumi 0.6.400 is released and it's backward compatible. How can a user of the sbt-jumi plugin configure it to use Jumi 0.6.400, without me having to release a new version of the plugin?

I would like to add a dependency to an sbt project which is only used for compilation. Neither should it be on the runtime class path, nor should it be visible in any form in the published POM. The idea is to add a stub only library ( OrangeExtensions ) so that the project can be compiled on any platform not just OS X. Is it possible like this somehow: libraryDependencies += "com.yuvimasory" % "orange-extensions" % "1.3.0" % ??? ? gourlaysama You can create a custom dependency configuration for this (actually, this is getting so common when you use private macros in your project, I wish SBT

I have build.gradle in front of me and there are some dependencies declared as provided but in documentation I do not see this dependency scope. dependencies { compile("org.springframework.boot:spring-boot-starter-web:1.2.4.RELEASE") .... provided 'backport-util-concurrent:backport-util-concurrent:3.1' provided 'org.javolution:javolution:5.5.1@jar .... } Is this provided by a plugin? If so how do I found out which plugin this belongs to? What is the difference between provided and runtime dependency scope in Gradle? What is provided scope? Suppose that a jar is needed to compile your code, but

I just upgraded to npm version 3 and noticed one of the biggest changes it made is that it enforces a flat dependency tree . Your dependencies will now be installed maximally flat. Insofar as is possible, all of your dependencies, and their dependencies, and THEIR dependencies will be installed in your project's node_modules folder with no nesting. You'll only see modules nested underneath one another when two (or more) modules have conflicting dependencies. So for example if package A is dependent on package B , when you npm install A you will get this file structure: --- root/ |--- node

I'm trying to understand this part: http://getcomposer.org/doc/02-libraries.md#lock-file this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project" Does that mean that if project P depends on library A, and library A depends on library B v1.3, project P won't care about the version of library B, and will possibly install B 1.4 instead? What's the point then? Or does it mean the opposite, as one would expect from a dependency manager? naderman Composer dependencies are defined in composer.json . When running composer install for the