Re: Unable to update version for provided transient dependencies

2020-05-28 Thread Tomo Suzuki
Hi Mitchell, Does your "mvn dependency:tree" contain the unwanted logging library? If yes, that's strange. Maven does not automatically include Provided transitive dependencies as far as I know. If not, then it's Storm that brought the library by reading the dependency graph in their way. On

Unable to update version for provided transient dependencies

2020-05-28 Thread Mitchell Rathbun (BLOOMBERG/ 731 LEX)
We are currently using Storm 1.2.3, and we want to update the version of log4j2 being used. In our Maven file, we specify storm-core with version 1.2.3 and provided scope. This dependency has dependencies on log4j-api, log4j-core, slf4j-log4j-impl, etc. The provided version of these

Re: Maven brings “test” transitive dependency as “compile”

2020-05-28 Thread Debraj Manna
Thanks Andy. It was a part of big multi-module project which I tried to extract out. So I missed excluding it in some places. On Wed, May 27, 2020 at 5:01 AM Andy Feldman wrote: > Thanks for an easy public reproduction! > > netty-common is coming through with compile scope from: >

[maven-assembly-plugin] tries to find tools.jar which does not exist in adoptopenjdk-11

2020-05-28 Thread Knoche, Heinz
Hello, I am wondering if someone could give me a hint regarding the following error when building a maven project (Maven 3.6.1, adoptopenjdk 11.0.6) "Could not find artifact com.sun:tools:jar:2.0.5 at specified path /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64/../lib/tools.jar" It seems to arise