The Center for Enablement team published a common application as a reusable module to
the central Nexus repository.
How can the common application be included in all API implementations?
A. Download the common application from Naxus and copy it to the src/main/resources
folder in the API
B. Copy the common application’s source XML file and out it in a new flow file in the
src/main/mule folder
C. Add a Maven dependency in the PCM file with multiple-plugin as
D. Add a Maven dependency in the POM file with jar as
D. Add a Maven dependency in the POM file with jar as
Explanation:
When a common application (like a shared utility, service, or framework) is published as a reusable module to a central Maven repository (e.g., Nexus), the correct and scalable way to include it in other Mule projects is to:
➡️ Add it as a Maven dependency in the pom.xml
➡️ Use jar as the classifier, because the common app is packaged as a Java archive (JAR) with reusable flows or libraries
This allows:
➡️ Consistent versioning across all projects
➡️ Reuse without duplicating code
➡️ Centralized management and updates
❌ Why other options are incorrect:
A. Download and copy to src/main/resources
🔸 Incorrect: Manual, not scalable, and breaks reusability and version control.
B. Copy the XML file to src/main/mule
🔸 Incorrect: Copy-pasting shared flows is bad practice. It creates code duplication and update inconsistencies.
C. Add a Maven dependency with mule-plugin as classifier
🔸 Incorrect: mule-plugin classifier is used for Mule plugin artifacts, not reusable shared JARs.