dependency-management

问题 I have a small groovy script that I want to edit and I have issues with the dependency management in Groovy. I am new to groovy and sorry in advance if this question is kinda studip / easy to answer. I use IntelliJ as IDEA. @Grab(group='org.jenkins-ci.main', module='jenkins-core', version='2.167', scope='provided') //import jenkins... def call() { Jenkins.instance.getItemByFullName(currentBuild.fullProjectName).getBuilds().each{ build -> if (currentBuild.number > build.number && exec != null)

问题 rpmbuild can autodetect dependencies by looking up shared libraries required by binaries included in the package and, while this is a good think almost every time, there are time when it is undesirable but only for some specific libraries. I am referring to the case where some binary file requires libraries that are not provided to the system via its rpm package management but installed directly by third party installers. Now, the question is: is there a way to keep the autodetect feature

问题 When IntelliJ opens a build.gradle file it will generate an IntelliJ project with the Gradle dependencies resolved and added to the project scope. This works great for the "compile" source set and the "test" source set, however I can not get this to work for custom source sets. I want to have IntelliJ resolve the dependencies for my componentTest source set. How do I tell IntelliJ to resolve these dependencies and add them to scope? dependencies { // main source set, "compile" scope in

问题 I'm using Ivy for project dependency management and it's been working well aside from one issue which I've always had. There are certain dependencies that Ivy is downloading but it's not installing them into my project. For example, log4j.jar is not being put in the project's lib folder even though it's listed as a dependency and is being downloaded successfully. Here's the output from my resolve: ivy-resolve: [ivy:configure] :: Ivy 2.2.0 - 20100923230623 :: http://ant.apache.org/ivy/ :: [ivy

问题 During my work with the Node.js environment, I faced the issue of version maintenance of Node.js modules. I would like to be sure that all internal Node.js modules are updated. Many of existing manuals focus just on how to update Node.js modules, but not how to automate such routine. The question: How to update all Node.js modules automatically to the latest version? Ideally, it should be some script, job, or task. 回答1: To update all Node.js modules manually: Open console with administrative

问题 I have too many files in .m2 folder where maven stores downloaded dependencies. Is there a way to clean all old dependencies? For example, if there is a dependency with 3 different versions: 1, 2 and 3, after cleaning there must be only 3rd. How I can do it for all dependencies in .m2 folder? 回答1: If you are on Unix, you could use the access time of the files in there. Just enable access time for your filesystem, then run a clean build of all your projects you would like to keep dependencies

问题 I am trying to compile all sub projects of one big project at my company into many jars with managed dependencies, so that not everybody who works at one project only needs to download the latest jars from a shared repository. ivy seems to be the solution for our problem, because ivy says that it integrates with ant (out build system) very well. But I cant get through the tutorials, they are all somehow more confusing than helpful. All I want to achieve for the beginning is to have two small

问题 I wanted to find unused dependencies in my project. Is there a feature for this in Gradle, like in Maven? 回答1: UPDATE: 28-06-2016: Android support to unused-dependency In June, 2017 , they have released the 4.0.0 version and renamed the root project name "gradle-lint-plugin" to "nebula-lint-plugin" . They have also added Android support to unused-dependency . In May 2016 Gradle has implemented the Gradle lint plugin for finding and removing unwanted dependency Gradle Lint Plugin: Full

问题 I am trying to build some kind of support for a maven-like dependency-management for our project. For this I add the pom I want to inherit from as a classpath dependency in the buildscript. I wrote a plugin that adds a task "inherit" that takes a file as Input and parses it and puts the dependencies from that pom into a map. The task is started in the apply method of the plugin where I get the pom from the classpath. static class InheritDependencyTask extends DefaultTask { @InputFile File

问题 I've created a Groovy project and build with Gradle from command line, all fine. But after load it into eclipse, I got lots of following errors inside the IDE. The project build path is pointing to these non-exist jars. Project 'nexus' is missing required library: 'C:\Users\jironghu.gradle\caches\modules-2\files-2.1\commons-beanutils\commons-beanutils\1.8.0\c651d5103c649c12b20d53731643e5fffceb536\commons-beanutils-1.8.0.jar' 回答1: My bad, the eclipse project was generated in another company