Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320940 - Deployment Assembly:Referenced Projects Classpath Entries in EAR project
Summary: Deployment Assembly:Referenced Projects Classpath Entries in EAR project
Status: RESOLVED INVALID
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.3   Edit
Assignee: Rob Stryker CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-26 13:37 EDT by Neeraj Agrawal CLA
Modified: 2011-06-02 04:08 EDT (History)
4 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 Neeraj Agrawal CLA 2010-07-26 13:37:50 EDT 
Build Identifier: 

"Referenced Projects Classpath Entries" in EAR project does not bring any value since EAR is not a java project. In my opinion the option should be removed.

Reproducible: Always
Comment 1 Max Rydahl Andersen CLA 2010-07-28 03:19:45 EDT 
Not sure I follow - the aggregating project does not have to be a java project to have project references to other java projects.
Comment 2 Neeraj Agrawal CLA 2010-07-28 09:20:37 EDT 
OK, but once you choose that option in EAR the dialog which pops up doesn't let you select anything.
Comment 3 Neeraj Agrawal CLA 2010-07-28 09:52:21 EDT 
So, i created EAR with EJB, Web projects

So now if I select Web project and select that option, i cannot choose EJb project either.
Comment 4 Carl Anderson CLA 2010-07-28 11:34:55 EDT 
Assigning to Rob for initial investigation.
Comment 5 Rob Stryker CLA 2010-07-29 08:22:19 EDT 
"Referenced Projects Classpath Entries" is currently the only UI to modify the .classpath file and add the properties / attributes that allow child projects to have references consumed by the ear. 

For example, if you have a web project with jars in it that need to "live" in the EAR, you must modify the .classpath file's attributes to add the custom tag which tells the EAR to pull those elements up. 

If we remove this UI, there then becomes zero UI to modify / add / remove this classpath attribute.  Until these issues are worked out, we are unable to remove this UI.
Comment 6 Neeraj Agrawal CLA 2010-07-29 09:53:17 EDT 
OK, i understand. But the current UI doesn't convey any information when that option is choosen.
Comment 7 Carl Anderson CLA 2010-09-23 14:07:26 EDT 
Rob, since 3.2.2 is declaring, I am retargetting to 3.2.3.  Please retarget as appropriate.
Comment 8 Rob Stryker CLA 2011-01-20 15:31:03 EST 
Retargeting old bugs... i'd be glad to have more discussion on this topic though if you have a better idea for UI
Comment 9 Rob Stryker CLA 2011-06-02 04:08:51 EDT 
This bug is out of date. The UI element in question is no longer present.