W-21370107 Updating Export Mule Project info#602
W-21370107 Updating Export Mule Project info#602Cristian-Venticinque wants to merge 1 commit intolatestfrom
Conversation
| The contents are lightweight because they don't include dependencies. | ||
| The IDE generates the dependencies configured in the `pom.xml` for the project. |
There was a problem hiding this comment.
This statement is not necessarily true because they can create shareable jar with or without dependancies. As long as the sources are attached, the project can be imported into ACB
| The terminal window in the IDE also provides the path to the JAR, in the `/target` directory under your project folder. In the desktop IDE, you can find the JAR file in the Explorer, under Java Projects: | ||
|
|
||
| image::int-export-deployable.png["Deployable JAR file in the Java Projects folder"] | ||
|
|
||
| File name patterns: | ||
|
|
||
| * Shareable JAR: `_application_name_-_version_-SNAPSHOT-mule-application-light-package.jar` | ||
| * Deployable JAR: `_application_name_-_version_-SNAPSHOT-mule-application.jar` |
There was a problem hiding this comment.
since the user can now set the file name and location in the export form, this information is outdated
| == Shareable JAR | ||
|
|
||
| When you export a Mule project, the shareable JAR file includes these files: | ||
| A shareable JAR file is lightweight, packaging only the source code of the application. The source code includes configuration files but not libraries or other dependencies required for your application to run and deploy successfully. |
There was a problem hiding this comment.
There are 3 export options:
- Deployable Jar: Takes the compiled code and package it in its distributable JAR with all its dependencies
- Deployable Jar + Attach Project Sources: Package into distributable JAR with source files and metadata needed to reimport the deployable file as an open Mule project.
- Sharable Jar: Takes the compiled code and package its source code only.
options 2 and 3 are shareable jars because they include project sources
There was a problem hiding this comment.
Option two is explained inside the conceptual section of the deployable Jar (line 30):
"A deployable JAR file contains the compiled code and all dependencies. For a deployable JAR, you can select Include project sources while exporting the project so the JAR can be opened in Anypoint Code Builder or Studio and also used for deployment. When this option is selected, the JAR also includes the configuration XML and other files in the
srcfolder (including resource files),mule-artifact.json, andpom.xml, the same project sources as in a shareable JAR. "
The == Shareable JAR and == Deployable JAR sections are not reflecting the UI options, rather they contain conceptual info about the differences between the two types of packages. Do you think this needs some adjustment?
2 participants
No description provided.