To export a utility project to a JAR file: You can also export the controls in a utility project to a control JAR. Note that if you use this process to create a JAR file from a utility project, then the controls within the JAR will not appear in the IDE correctly (although they will work correctly). Include the source files only if you wish to view/edit source at the destination. The most common reason to export a WAR file is to deploy for production, and in that case, the source files should not be included. If you wish to include the Java source files in your archive, you must check this option. Normally the Export source files option is unchecked. Use the Browse button to specify the location of the WAR file.

Use the pulldown to select the web project in the Web module box.

The most common reason to export an EAR file is to deploy for production, and in that case, the source files should not be included. If the file already exists, you must check the Overwrite existing file selection to replace the existing file. Use the Browse button to specify the location where the new EAR file will be located.

Use the pulldown to select the EAR project in the EAR application box.Right click anywhere on the Project Explorer view and choose Export from the menu.How to Export an Enterprise Application Project to an EAR However this is only a useful feature for creating utility JAR files for sharing code. For example, you can use the Archive and JAR file options of the Export dialog to create JAR files for EJB and web projects. Note that options on the Export dialog that are not described in this documentation do not apply to Workshop for WebLogic projects. Export Controls in a Utility Project to a Control JAR.

Export an Enterprise Application Project to an EAR.

Web project (Web Service Project, Dynamic Web Project)

How to use eclipse to export project