You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have explicitly included commons-io 2.15.1 dependency in Pom.xml so that the project uses this version and ignores the others.
My first impression is that there's a dependency clash for commons-io. Since I am pretty new with Java & inexperienced with it, I would like to know if there's a way to solve this dependency clash.
is wrongly included (note the ! sign in the <!dependency> tag) which makes the whole pom invalid, so I presume in the real project it's included correctly. It is old and does not exist in most recent versions of Jersey.
You can check dependencies of a maven project using
mvn dependency:tree
however, if you want to exclude some 4th party dependencies from dependencies of your project, it's possible to apply:
In one our projects, we use the following packages:
jersey-server (2.28)
&poi-ooxml(5.2.5)
. Both these packages havecommons-io
as sub-dependencies.While
poi-ooxml
uses2.15
version ofcommons-io
,jersey
uses2.11
version, irrespective if we upgrade thejersey
to its latest release (https://github.com/eclipse-ee4j/jersey/blob/3.1.8/tools/jersey-release-notes-maven-plugin/pom.xml#L77).When we run the project, we get the following error:
We have explicitly included
commons-io 2.15.1 dependency in Pom.xml
so that the project uses this version and ignores the others.My first impression is that there's a dependency clash for
commons-io
. Since I am pretty new with Java & inexperienced with it, I would like to know if there's a way to solve this dependency clash.pom.xml
The text was updated successfully, but these errors were encountered: