I have a Gradle build script containing the following dependencies (and not much else):
dependencies {
testCompile "com.foo:lib-foo:2.0.0-SNAPSHOT"
testCompile "com.foo:lib-bar:2.0.2-SNAPSHOT"
}
The dependencies are resolved from a Maven…
We have a Gradle Java project, and our build.gradle has various module dependencies. Suppose two of those module dependencies are dependencyA and dependencyB:
dependencies {
implementation 'org.example.dependency:dependencyA:0.13.0'
…
I have a dependency that transitively includes a runtime dependency org.springframework.boot:spring-boot-starter-log4j2 which I want to exclude.
I have tried:
dependencies {
"implementation" ("com.meanwhileinhell.common:my-lib:${commonVersion}")…
I have a java project which has a couple of dependencies, e.g.:
dependencies {
compile("com.whatever.jar:jar-1:1.2.3")
compile("com.whatever.jar:jar-2:4.5.6")
compile("com.whatever.jar:jar-3:7.8.9")
}
I package it as a jar library and…
The Maven enforcer plugin is identifying a code convergence issue with a 3rd party library I'm using. How can I ignore this whilst still running the enforcer plugin on the project over the rest of the project or how else should I resolve the issue…
In my angular project, I recently upgraded rxjs to version 6. Now, a module from npm (inside the node_modules folder) is failing because of some breaking changes (old imports don't work anymore). I adapted the imports for my code, but how can I fix…
ProjectA references ProjectB
ProjectB references ProjectC
ProjectA has PackageReference in the .csproj
Given the above, it is possible to directly reference ProjectC types in ProjectA. This is undesirable…
I referred to this thread differences between dependencymanagement and dependencies in maven but this question is specific.
Parent POM:
com.company.rtdp.rtds
…
During build via Gradle I got this
POM relocation to an other version number is not fully supported in Gradle : xml-apis:xml-apis:2.0.2 relocated to xml-apis:x
ml-apis:1.0.b2.
Please update your dependency to directly use the correct version…
I have a maven project that I'd like to share with several of my other projects. It has some custom code, and then a few dependencies on things like log4j, jasypt, etc.
I build it and install it to my local maven repo. I can see it's successfully…
In a project using Java 8, joda-time is a transitive dependency of a project dependency. I want to enforce use of java time instead of joda-time in project source. How can joda-time classes be restricted to be used in project source in a gradle…
So I have a project over here that has the following build.gradle:
// PLUGINS
plugins {
id 'java' // or 'groovy' Must be explicitly applied
id 'com.github.johnrengelman.shadow' version '1.2.2'
}
apply plugin: 'application'
apply plugin:…
