What export options should be selected to create the smallest JAR file that can be imported into other developer’s Anypoint Studio and run successfully?

Mule application contains ActiveMQ JMS dependency. Mule application was compiled and run successfully in Anypoint Studio. The mule application must now be exported from Anypoint Studio and shared with other developer.

What export options should be selected to create the smallest JAR file that can be imported into other developer’s Anypoint Studio and run successfully?
A . Select only Attach Project Sources only
B. Select both Attach Project Sources and Include project modules and dependencies option
C. Select the Include project modules and dependencies option only
D. De-select both Attach Project Sources and Include project modules and dependencies option

View Answer

Answer: A

Explanation:

Correct answer is Select only Attach Project Sources only

You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace.

Deselect the Include project modules and dependencies option.

This option skips bundling the actual modules and external dependencies required to run the Mule application in a Mule runtime engine, creating a lightweight JAR file package that does not include any dependencies specified in the Mule application’s pom.xml file.

The generated JAR file is not a functional deployable archive and cannot be deployed to a Mule runtime engine, but instead offers a way to archive only the source files that make up the Mule application. This is the same as using the -lightWeightPackage flag when

packaging using the Mule Maven Plugin and is useful if you want to distribute your project to other Studio installations because it only keeps a reference to all its dependencies. When you import a lightweight package into Studio, all your dependencies are automatically downloaded MuleSoft Doc

Ref: https://docs.mulesoft.com/studio/7.8/import-export-packages