App Connect

 View Only

 ACE v13 Map Compilation Fails with NoClassDefFoundError for Maven Dependencies

Francis Cocx's profile image
Francis Cocx posted Tue February 10, 2026 08:39 AM

After migrating from ACE v12 to ACE v13, our ibmint package --compile-maps-and-schemas builds are failing with NoClassDefFoundError during map compilation, even though the required JARs are present in the Maven repository and are being added to the BAR file.

java.lang.NoClassDefFoundError: com.m2.repo.path.common.onfiguration.ConfigException
    at java.base/java.lang.Class.getDeclaredMethods(Class.java:1202)
    at com.ibm.msl.mapping.xquery.codegen.generators.BaseXQueryGenerator.generateWrapperCode(BaseXQueryGenerator.java:2907)
    ...
Caused by: java.lang.ClassNotFoundException:  com.m2.repo.path.common.configuration.ConfigException
    at com.ibm.broker.classloading.base.MbClassLoader.loadClass(MbClassLoader.java:182)

We have a Java project that depends on the utilityJAR. And we have added this to our pom as a dependency:

<dependency>
    <groupId> com.m2.repo.path</groupId>
    <artifactId>UtilityJar</artifactId>
    <version>UtilityJar_V13-SNAPSHOT</version>
    <scope>provided</scope>
</dependency>

The error occurs specifically during the map compilation phase when the compiler tries to introspect Java compute node classes that reference types from the provided dependency. Other Maven dependencies (like slf4j) work fine because they're only used in field declarations, not in method signatures or exception handling.

Adding UtilityJar as an explicit project reference in the consuming project's .project file and adding --project UtilityJar to the ibmint command resolves the issue.

When executing the same ibmint command on v12 the command completes successfully. 

The questions I have are:

  1. Is this a breaking change in ACE v13's dependency resolution? In v12, the map compiler seemed to resolve Maven dependencies, but v13 appears to require explicit .project references.
  2. Is there a better solution than adding project references to every project that require those dependencies? We have many projects that depend on jars like this, and adding explicit references everywhere is not maintainable.
  3. Is this the intended behavior, or is it a bug? The fact that it worked in v12 suggests this might be unintended.

Thanks!

Related Content