Just as an alternative: there is also since 3.9 the "reverse dep tree":
https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L96-L104
Just pass to Maven `-Dmaven.repo.local.recordReverseTree` and Maven
Hi David,
On Saturday , 29. July 2023, 01:29:14 CEST David Karr wrote:
> In general, I know how to override transient artifact versions. You add an
> "exclusion" for the artifact on the dependency that is including that
> dependency, and then you manually add that dependency in the same pom where
Hi David,
When I want to know what's bringing in a dependency I use
https://github.com/ferstl/depgraph-maven-plugin
mvn depgraph:aggregate -DtargetIncludes=:jackson-databind
And it drops a nice diagram in the root build dir.
com.github.ferstl
depgraph-maven-plugin
David Karr wrote:
> I've been struggling with trying to do this, along with trying to
> understand the output of "mvn dependency:tree" and the apparently
> functionally similar output in the "Dependency Hierarchy" view in Eclipse
> using the m2e plugin. Although I can loosely see the
We actually already use several different BOMs, both internal and external.
It didn't occur to me to look for a jackson-bom, and that's a good idea.
However, I assumed that would just be a cosmetic change, but on the first
try it seemed like that made it work. I need to do some cleanup, but I
Hi David,
You could try to add the Jackson BOM in the parent dependencyManagement.
That would override all versions in the (transitive) dependencies of the
child modules. For a nice explanation of BOM files, see Baeldungs blog post
[1].
4.0.0
baeldung
Test
0.0.1-SNAPSHOT
pom
In general, I know how to override transient artifact versions. You add an
"exclusion" for the artifact on the dependency that is including that
dependency, and then you manually add that dependency in the same pom where
you added the exclusion. In my case, the version I want is defined in a
bom
