Home/ Questions/Q 5838185
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T11:26:28+00:00

I have a maven build which generates some duplicated JARs in classpath. Here are

  • 0

I have a maven build which generates some duplicated JARs in classpath.

Here are some examples:

groupId: javax.xml.stream
artifactId: stax
version: 1.0-2

groupId: stax
artifactId: stax
version: 1.0.1

groupId: jboss
artifactId: javassist
version: 3.7.0 GA

groupId: javassist
artifactId: javassist
version: 3.9.0 GA

These JARs are not imported directly from my project, they are transitive dependencies. Since the groupId and artifactId of the different versions does not matches, maven thinks that they are independent.

I can hunt down (may be using some tool for that) these duplicates and exclude them explicitly in pom.xml. However I don’t want to manually hunt them down and exclude them, because this defeats the automatic dependency managing from maven and is a nightmare when some dependency is upgraded and the transistive dependencies mismatches again. There exist some way to make maven smarter and fix this automatically?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Answering that. I found no way to make maven smarter and had to hunt down and manually exclude every duplicated dependency. Switching the repositories to use a set of repositories that does not messes up one to the other helps too, but this is not always possible and can have side-effects of breaking some dependencies.

    • 0