| Summary: | Manifest entries with backslash are not handled correctly by manifest page in deployment assembly page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Common Tools | Reporter: | Aidyl Kareh <amkareh> | ||||
| Component: | wst.common | Assignee: | Aidyl Kareh <amkareh> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Carl Anderson <ccc> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | amkareh, jsholl | ||||
| Version: | 3.2.2 | Flags: | ccc:
review+
jsholl: review+ |
||||
| Target Milestone: | 3.2.3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Aidyl Kareh
Created attachment 184803 [details]
Proposed Patch
The problem is caused because manifest entries are broken down to IVirtualReference objects and the backslash gets lost in the process (breaks the entry down to runtime path and archive name). This patch updates the code so that if a backslash is found, then the archive name is set to the whole manifest entry and the runtime path is set to an empty value.
Code checked into 32M and HEAD for WTP 3.2.3 and 3.3 |