dependency-management

I have a non-standard project layout. How can I use Gradle to just download a bunch of JAR dependencies into a lib directory, under the same directory where build.gradle is? For now, I don't need it to do anything else. Here is what I have so far: apply plugin: "java" repositories { mavenCentral() } buildDir = "." libsDirName = "lib" dependencies { runtime group: "...", name: "...", version: "..." } If I run gradle build , it builds an empty JAR file in the lib directory, instead of downloading my dependencies there. Switching "lib" with "." in the properties does not work either. Something

I'm worried about the situation when libraries Foo and Bar each expose a resource on the classpath with the same name, say properties.txt in this example. Assuming a Maven set up and the jars are deployed with Maven, if I have this set up: Library Foo: $ cat Foo/src/main/resources/properties.txt $ Foo and Library Bar: $ cat Bar/src/main/resources/properties.txt $ Bar And an App that depends on them, whose pom looks something like this - in a nutshell this just says "build a jar-with-dependencies, and depend on Foo and Bar : <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven

So "myLibrary" references "anotherLibrary". Both libraries follow http://semver.org/ If I release a new version of myLibrary that forces consumers to update to a new major version of anotherLibrary should the major version of myLibrary also increment? This is specifically answered in the FAQ section of semver, where it is recommended that the major version be not bumped up. http://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api It really depends on if the public API of the main library changes. I tend to treat libraries as a black box. I don't need

As part of a major refactoring of my Node.js app (going DDD), I'm looking for a library that through inspecting code is able to visualize module dependencies (by means of 'requiring' them) between different node-modules. Visualizing in Table-format is fine, I don't need fancy graphs. Any Node libraries out there? I do not know if this exists, but I found the following by quick search : http://toolbox.no.de/packages/subdeps http://toolbox.no.de/packages/fast-detective Maybe subdeps is not exactly what you want right now, but I think you could use these projects to make that project yourself? If

I am quite new to gradle, so maybe I am asking something quite easy.... I am looking for a solution to put all dependencies in scope testCompile into a zip file. I checked http://forums.gradle.org/gradle/topics/how_do_i_make_a_zip_to_contain_dependency_artifacts but this seems to work only for runtime dependencies. I also checked http://www.gradle.org/docs/current/userguide/working_with_files.html Chapter 16.8, but that did not work either. When I access via configurations.testCompile.allArtifacts.files , my zip is always empty. When I acces via configurations.testCompile.allDependencies I can

After removing a dependency from composer.json and running install or update, should I expect the files to be removed automatically from disk? I had to remove them manually, not sure if I am supposed to. Running a composer update will remove packages you removed from your composer.json. Since install uses composer.lock instead of composer.json it will not remove packages removed from your composer.json . However, you should get a message that your lock file is out of sync with your composer.json and you should run an update. 来源： https://stackoverflow.com/questions/11680395/should-dependencies