Fixing conflicts with tier-parties
Your project dependencies are not the only artifacts that can raise conflicts—most of the time, a Java/JEE application is not purely standalone—and it lays on a tier application or container, which is either an application server or anything else. However, these tier applications embed their own dependencies—the amount of which can be in dozens—conflicts between resident application and host dependencies often happen. You have full interest to anticipate these conflicts and treat the problems ahead. The question that arises: "How to deal with them?"
Let's consider the artifact
com.packt.dependencyManagement.chapter6:conflictWithTiers. It was generated through an archetype:
mvn archetype:generate -B \ -DgroupId=com.packt.dependencyManagement.chapter6 ...