In the most common case, the artifacts needed at compile time are a subset of those needed at runtime. For example, let’s say that a program called app uses library foo, and library foo internally uses library bar. Then only foo is needed to compile app, but both foo and bar are needed to run … Read more
If you want to actually view the library dependencies (as you would with Maven) rather than the task dependencies (which is what inspect tree displays), then you’ll want to use the sbt-dependency-graph plugin. Add the following to your project/plugins.sbt (or the global plugins.sbt). addSbtPlugin(“net.virtual-void” % “sbt-dependency-graph” % “0.9.2”) Then you have access to the dependencyTree … Read more
It can be quite useful sometimes to get the latest release – if for example you release often your own dependencies. You can get the latest version like compile “junit:junit:+” or better specify at least the major version like compile “junit:junit:4.+”
There was a really nice post on the Spring Blog from Keith Donald detailing howto Obtain Spring 3 Aritfacts with Maven, with comments detailing when you’d need each of the dependencies… <!– Shared version number properties –> <properties> <org.springframework.version>3.0.0.RELEASE</org.springframework.version> </properties> <!– Core utilities used by other modules. Define this if you use Spring Utility APIs … Read more
If you are using a GNU compiler, the compiler can assemble a list of dependencies for you. Makefile fragment: depend: .depend .depend: $(SRCS) rm -f “$@” $(CC) $(CFLAGS) -MM $^ -MF “$@” include .depend or depend: .depend .depend: $(SRCS) rm -f “$@” $(CC) $(CFLAGS) -MM $^ > “$@” include .depend where SRCS is a variable … Read more
Does this help? http://jlorenzen.blogspot.com/2009/06/maven-global-excludes.html “Assuming I want to exclude avalon-framework from my WAR, I would add the following to my projects POM with a scope of provided. This works across all transitive dependencies and allows you to specify it once. <dependencies> <dependency> <artifactId>avalon-framework</artifactId> <groupId>avalon-framework</groupId> <version>4.1.3</version> <scope>provided</scope> </dependency> </dependencies> This even works when specifying it in … Read more
Most likely, one of your dependencies uses the kotlin version of the viewmodel library whereas your code uses the java version. Specify both to enforce the latest version for all dependencies: def lifecycle_version = “2.4.0” implementation “androidx.lifecycle:lifecycle-viewmodel:$lifecycle_version” implementation “androidx.lifecycle:lifecycle-viewmodel-ktx:$lifecycle_version”
If buildscript itself needs something to run, use classpath. If your project needs something to run, use compile. The buildscript{} block is for the build.gradle itself. For multi-project building, the top-level build file is for the root project, the specific build file is for sub-project (module). Top-level build file where you can add configuration options … Read more
It is only a warning as it won’t actually stop your code from running, It’s just there to give you a heads up that there’s something wrong with your dependencies. Effectively, peer dependencies are a way for packages to specify, “to use me, you should also have x version of y package installed”. You should … Read more
Try setting PERL_MM_USE_DEFAULT like so: PERL_MM_USE_DEFAULT=1 perl -MCPAN -e ‘install My::Module’ It should make CPAN answer the default to all prompts.