| Summary: | Manifest entries not showing correct paths if the module's deploy path was modified | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Aidyl Kareh <amkareh> | ||||
| Component: | jst.j2ee | Assignee: | Aidyl Kareh <amkareh> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Chuck Bridgham <cbridgha> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | amkareh, ccc, jsholl | ||||
| Version: | 3.2 | Flags: | cbridgha:
review+
jsholl: review+ |
||||
| Target Milestone: | 3.2.2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Aidyl Kareh
Created attachment 176937 [details]
Proposed Patch
The attached patch updates the JEEManifestDiscerner class so that instead of just using the reference's deploy path when creating the a manifest entry, now the deploy path of the project that owns the MANIFEST.MF file is also taken into consideration. The ClassPathSelection class was also updated to handle this scenario.
approved checked into head for wtp 3.2.2 fixed |