| Summary: | Deployment Assembly:Referenced Projects Classpath Entries in EAR project | ||
|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Neeraj Agrawal <nagrawal> |
| Component: | jst.j2ee | Assignee: | Rob Stryker <stryker> |
| Status: | RESOLVED INVALID | QA Contact: | Chuck Bridgham <cbridgha> |
| Severity: | normal | ||
| Priority: | P3 | CC: | andrey.melentyev, cbridgha, ccc, manderse |
| Version: | 3.2 | ||
| Target Milestone: | 3.3 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Neeraj Agrawal
Not sure I follow - the aggregating project does not have to be a java project to have project references to other java projects. OK, but once you choose that option in EAR the dialog which pops up doesn't let you select anything. 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. Assigning to Rob for initial investigation. "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. OK, i understand. But the current UI doesn't convey any information when that option is choosen. Rob, since 3.2.2 is declaring, I am retargetting to 3.2.3. Please retarget as appropriate. Retargeting old bugs... i'd be glad to have more discussion on this topic though if you have a better idea for UI This bug is out of date. The UI element in question is no longer present. |