The Deployment Assembly project
property page is shared among all Java™ EE project types, including Aries projects.
Procedure
- Editing your EAR project deployment assembly page:
- To use the Deployment Assembly page, right-click your
EAR project and select . The Deployment
Assembly page consists of a table containing a Deploy Path column
and a Source column:
- The deploy path column represents the path within the
packaged archive. Click Add to add mappings: These are the possible references
you can add:
- Archive via path Variable
- Archives from File System
- Archives from Workspace
- Folder
- Project: allows bundling of the project into an archive,
and placed in the runtime location specified. Project references are
often used to bundle utility projects into a web project (WEB-INF/lib)
location, which is automatically included on the War's runtime classpath.
- The Source column represents the project path. For information
about Annotation scanning, see Excluding files from annotation scanning.
- Editing your EJB or web project deployment assembly page:
- To use the Deployment Assembly page, right-click your
Java EE project and select . For Java
EE modules the page consists of two tabs:
- The Deployment Assembly tab: the Deployment Assembly page consists
of a table containing a Deploy Path column and a Source column.
- The Manifest Entries tab
- On the Deployment Assembly tab, click Add to add mappings: These are the possible references you
can add:
- Archive via path Variable
- Archives from File System
- Archives from Workspace
- Folder
- Java Build Path Entries
- Project: allows bundling of the project into an archive,
and placed in the runtime location specified. Project references are
often used to bundle utility projects into a web project (WEB-INF/lib)
location, which is automatically included on the War's runtime classpath.
- On the Manifest Entry page, click add to add manifest entries: Click Add to add manifest entries: