Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332232 - Allow Deployment tagging of Java Containers that contain both jar and project references
Summary: Allow Deployment tagging of Java Containers that contain both jar and project...
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Roberto Sanchez Herrera CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard: Maven
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-09 13:38 EST by Chuck Bridgham CLA
Modified: 2012-05-01 15:54 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chuck Bridgham CLA 2010-12-09 13:38:50 EST 
Currently, the classpath tagging support for module assembly allows tagging classpath containers, and in the case of J2EE 1.4 module's - generates MANIFEST entries corresponding to each contained jar file.  If the container also had project references, these are ignored in the MANIFEST generation.

This enhancement would change the MANIFEST generation code to also support project references, and add an api to set/retrieve the "archive name" of the project at runtime.
Comment 1 Chuck Bridgham CLA 2011-09-29 10:19:18 EDT 
removing from plan for now....   may add later