Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322542 - Separate "consumed" classpath containers from Ear Libraries
Summary: Separate "consumed" classpath containers from Ear Libraries
Status: CLOSED DUPLICATE of bug 318068
Alias: None
Product: WTP Common Tools
Classification: WebTools
Component: wst.common (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: wst.common CLA
QA Contact: Carl Anderson CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-12 10:43 EDT by Chuck Bridgham CLA
Modified: 2010-08-20 17:24 EDT (History)
3 users (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-08-12 10:43:35 EDT 
The summary points out a specific case, but this bug addresses the issue in general.  Classpath containers added to the deployment assembly should be used as JDT intended, not absorbed into the component dependency mechanisms, and only exposed as such.

Specifically - Containers, and their contents should be added as a .classpath entry to the client projects of the Ear.

The Ear project using the "container" is not a good example, because this is not a JDT "Java" project, and they can't be added directly.

But the current usecase is for a "container" or fileset of jar's to be bundled and deployed into the Ear. But "classpath" of the client modules is changed to include this container.  

Also - This reference type could also be renamed to be clear how its used. (fileset)
Comment 1 Konstantin Komissarchik CLA 2010-08-12 10:58:49 EDT 
Note that this really isn't an enhancement as the current Helios approach is a major compatibility issue for third party containers.
Comment 2 Konstantin Komissarchik CLA 2010-08-20 17:24:49 EDT 

*** This bug has been marked as a duplicate of bug 318068 ***