dependency-management

问题 This question already has answers here : Differences between dependencyManagement and dependencies in Maven (12 answers) Closed 2 years ago . I already create a jar that contain some common jars, which we will use it in different applications and can be used via many users. To Solve this, i create a common jars, so i can control this commons jars and version of them, then store it in nexus server, so it can contain the parent pom and can be used by many developers. So i create a simple maven

问题 I have a jar dependency that resides on a remote server. How do I resolve that in Gradle? There doesn't seem to be a way to define a repository for remote files, only local files, and I'm something like this doesn't seem to work either: compile("group:name:version") { artifact { url = "http://server/dep.jar" } } The docs seems to hint that something like this should be possible, but so far I'm unable to find an example anywhere. Support for non-managed dependencies: If your dependencies are

问题 I have a Gradle project that I want to import to Versioneye to check if my dependencies are up to date, but it's a complex config file (with external variables etc.) and Versioneye does not manage to handle the dependencies properly. I don't want to install the Versioneye gradle plugin. How can I export the dependencies from my repo to Versioneye? 回答1: You can list all the dependencies gradle app:dependencies . With a bit of string manipulation, you can export a "clean" dependencies file and

问题 I try to import this OSGI bundle [2]enj-library into eclipse (after compiling it with Maven) , I used: "File > Import...> Plug-in Development > Plug-ins and fragments" and I imported the binary but I got the following unresolved dependencies: These dependencies were mentionned in pom.xml: <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <version>1.2.1</version> <extensions>true</extensions> <configuration> <manifestLocation>META-INF</manifestLocation>

问题 I have 2 private pods. Let's call them PrivateA and PrivateB . These used to not depend on each other, so I could use them both in my project pretty easily like so: source 'http://my-private-domain.com/PrivateA.git' source 'http://my-private-domain.com/PrivateB.git' source 'https://github.com/CocoaPods/Specs.git' target 'MyProject' do use_frameworks! # Pods for MyProject pod 'PrivateA', :git => 'http://my-private-domain.com/PrivateA.git' pod 'PrivateB', :git => 'http://my-private-domain.com

问题 I observed a strange behaviour in my maven 3.0.5 / JDK 1.7 build. Within the dependency tree I found TEST -resources that have transitive COMPILE dependencies (see section 1 below). This triggers than in a subsequent build phase that maven-jira-plugin:4.2.20 unpacks these resources to the target/class folder (In effect this is the expected/normal behaviour, but not desired here, see section 2 below) On an other machine, (same Maven/JDK version) these dependencies are not marked as COMPILE and

问题 I have a savant repository in my project and I want to add all of the jars contained within the repo to IntelliJ's depenedcies list. I can add the jars one at a time, but I want to be able to add them all at once. Is there a way to add all the jars found within all the directories/subdirectories? Details: IntelliJ 12 Update: I can not change the repository structure, it is auto populated when ant builds. 回答1: Adding jars from a directory is supported, but not recursively, please vote for this

问题 According to the pub get docs the main difference between pub get and pub upgrade is: If a lockfile already exists, pub get uses the versions of dependencies locked in it if possible. If a dependency isn’t locked, pub will get the latest version of that dependency that satisfies all the version constraints. This is the primary difference between pub get and pub upgrade, which always tries to get the latest versions of all dependencies. But this leaves me with a few questions. What do they

问题 I am currently writing my first Gradle build script to help structure a simple Java app to be used from the command line. Below is the full build.gradle code apply plugin: 'java' apply plugin: 'eclipse' defaultTasks 'clean', 'build' repositories { mavenCentral() } jar { baseName = 'napier-deploy' version = '1' manifest {attributes 'Main-Class': 'com.Main'} } dependencies { compile 'org.apache.httpcomponents:fluent-hc:4.3.3' compile 'org.apache.httpcomponents:httpclient-cache:4.3.3' compile

问题 Concerning the pom.xml Maven file: Is there any specific rule to apply to the ordering of declared sections? Does it have any importance or impact on the build? Shall I follow any official convention? 回答1: Although in most of the cases it is irrevant whether one section is declared before another, readeabilty could be indeed impacted when choosing a weird layout (e.g. Maven coordinates at the end). But that's not the most important point, because yes , ordering of certain elements can impact