Daniel Demesmaecker wrote:Which idea are you using? For intelij by example if you go to your projectstructure and click on problems you can see if there are any issues with your dependencies.
Most likely your idea will also red underline them in your pom and they will simply not work...
Stephan van Hulst wrote:You can use the maven-dependency-plugin to perform all kinds of useful operations to check your dependencies.
For instance, executing mvn dependency:tree -Dverbose will show a dependency tree that includes conflicting dependencies.
Stephan van Hulst wrote:"Omitted for..." means that a dependency wasn't included, because it was either already included earlier, or because it conflicts with a dependency that was already included but has a different version.
"Omitted for duplicate" is fine, and happens a lot. You can still try to eliminate these by not declaring these dependencies in your POM if they are already included as transitive dependencies.
You really should try to get rid of all "Omitted for conflict" notices however, by explicitly excluding the version that you don't want. Even if you've removed all conflicts this way, it's never certain if everything will be okay, because the version that you included in your project may not be backwards compatible with the version that one of your dependencies requires. The only way to find out is to thoroughly test your application.