Guide - IOM 2.13 Migration of Customization - Internal

Product Version


Product To Version



1 Dependencies provided by Application Server or IOM Artifacts

There are two types of Maven dependencies that are now set to the scope provided:

  1. Artifacts provided by Wildfly/JBoss
  2. Artifacts provided by other IOM artifacts

They are not redundantly deployed with IOM artifacts anymore. Since provided dependencies are not transitive, those dependencies have to be stated explicitly in every project depending on them as it is also best practice.

This affects customization artifacts that are depedending on artifacts which were compile or runtime dependencies of IOM, so that they could have been used transitively without stating them explicitly (not recommended). Adding those dependencies to the POM with the scope provided should resolve build failures.

Common examples for dependencies provided by Wildfly:

  • com.fasterxml.jackson.core:jackson-core
  • com.fasterxml.jackson.core:jackson-databind
  • com.fasterxml.jackson.core:jackson-annotations
  • commons-io:commons-io


The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Customer Support
Knowledge Base
Product Resources