When the mule-maven-plugin is updated, it may not correctly infer or include the necessary mule-apikit-module dependency, or the implicitly resolved version might be incompatible with the updated plugin or Mule Runtime. Explicitly declaring the mule-apikit-module dependency in your project's pom.xml ensures that the correct and compatible version of the APIKit module is used during the build process, resolving compilation failures.
To resolve APIKit build errors after updating the Mule Maven Plugin, explicitly add or update the mule-apikit-module dependency in your project's pom.xml file.
Ensure you use a version compatible with your Mule Runtime and mule-maven-plugin. For example, if using Mule Runtime 4.11.5 and mule-maven-plugin 4.9.1, you can use mule-apikit-module 1.11.17.
After making this change, perform a clean build to ensure all dependencies are correctly resolved:
005388491

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.