Bugzilla – Full Text Bug Listing
| Summary: | Lib directory not being used as Default deploy path for utility projects | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Scott Huff <shuff> | ||||||
| Component: | jst.j2ee | Assignee: | Scott Huff <shuff> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Chuck Bridgham <cbridgha> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | jsholl | ||||||
| Version: | 3.2 | Flags: | cbridgha:
review+
jsholl: review+ |
||||||
| Target Milestone: | 3.2.1 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 173161 [details]
patch
Tweaked previous patch... checking for null lib dir
approved This was dropped to HEAD |
Created attachment 173146 [details] Patch file alters AddComponentToEnterpriseApplicationDataModelProvider.java RESOLVED by: returning a map of utility project components to the lib directory when the default component deployment path map is generated. previously a null map was returned, resulting in "/" for all component types being added to the ear. Bug occurrence: when creating a new Utility project from the new utility project wizard with "add to ear" selected, OR when adding an existing utility project to an Ear during Ear creation, the Utility project should be deployed to the lib directory by default