Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320534 - Custom location path for new Ear modules not being used used.
Summary: Custom location path for new Ear modules not being used used.
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2.2   Edit
Assignee: Scott Huff CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-21 13:10 EDT by Scott Huff CLA
Modified: 2010-08-10 17:27 EDT (History)
2 users (show)

See Also:
cbridgha: review+


Attachments
Patch file for new Ear module creation (1.97 KB, patch)
2010-07-21 13:10 EDT, Scott Huff CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Huff CLA 2010-07-21 13:10:44 EDT
Created attachment 174883 [details]
Patch file for new Ear module creation

Steps to recreate bug: 
1. File->New -> Enterprise Application Project 
2. In the new Ear project wizard,
    -enter "MyEarProject" as the project name;
    -uncheck "use default" in the content section;
    -enter c:\javasource\MyEarProject in the directory field;
    -click Next. 
3. Click New Module... 
4. Uncheck “Create default modules”. 
5. Click the "Web" radio button and click Next.
6. In the new web project wizard,
    -enter "MyWebProject" as the project name;
    -uncheck "use default" in the content section;
    -enter c:\javasource\MyWebProject in the directory field
    -click Next. 
7. Click Finish. Click Finish. 

MyEarProject is created in C:\javasource\MyEarProject location, which is correct, But MyWebProject is put in your current workspace folder,
 which is not correct.

(Note: this bug also occurs when any other module type radio buttons is selected
         in step 5)

The patch file included fixes the issue by preventing the new wizards properties from being improperly over-written.
Comment 1 Jason Sholl CLA 2010-07-21 14:10:16 EDT
this is the same fix as the 305P bug 320536
Comment 2 Chuck Bridgham CLA 2010-08-10 16:05:12 EDT
approved
Comment 3 Jason Sholl CLA 2010-08-10 17:27:51 EDT
code checked into head for WTP 3.2.2