1. Customize how to deploy the project MyEclipse supports the use of flexible deployments for assembly deployment of projects, and flexible deployment support allows you to customize how the final archive is assembled. For example, you can map only a subset of the source folder, deploy it in a path where the project's project doesn't exist, and usually deviate from a fixed project structure, everything will reside in your project's WebRoot folder. . Deployment of enterprise projects, compressed file names, and utility projects can also be controlled here. To configure the deployment component, right-click the project, select Properties, MyEclipse Extensions from the menu, and select Deploy Components. Default EAR project deployment component 2. Add library, file, or project deployment You can easily add user libraries, files, or application projects to deploy. Click the Add button from the Deployment Component Properties page. Adding new resources to the deployment component When you add resources to the EAR's deployment assembly, the additions are reflected in the project module's EAR library container. The Java projects that are added by default are placed in the .jar library in the lib folder. Adding a resource's default path to deploy the EAR module library reflects the addition 3. Custom deployment name and JAR path You can change the default deployment name and JAR path by simply double-clicking the deployment path. If the creation project occurs in the project, changes to the module deployment URI are reflected in the application.xml. Note: If the archive you changed is the LIB default path, you must add the resource to the list of modules for the archive you need to access. See the configuration manifest directory. Changing the deployment name of a .JAR 4. Mapping a custom folder to a new deployment path In an EAR project, you might want to create a folder for a set of custom libraries. For example, using the Expand component, you can map the folder to the lib folder so that you can access the EAR module through the library. In the example below, the CustomLibs folder is added to the deployment assembly and its deployment path is changed to a library. The files in the CustomLibs folder will be displayed in the module EAR library. Changing the mapping of custom library folders 5. Configuring inventory entries If you add a library for an EAR module or change the deployment path for an EAR project library, you must add resources to the module project so that the library can reference the deployment manifest at development time. The libraries in the EAR lib folder are automatically referenced by the EAR module. Other libraries, including those that reside in the EAR root directory, must be referenced by MANIFEST.MF. In the following example, the library deployment path in the EAR deployment component is changed from lib to another path, including the libraries in the EAR module library, and the library is added to the module list. Add a list entry to the module