Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358652 - Uncheck and check of the Java Facet in the FacetConfigurationDialog causes the Java output folder to change in the Dynamic Web Project wizard.
Summary: Uncheck and check of the Java Facet in the FacetConfigurationDialog causes th...
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3.2   Edit
Assignee: Rosendo Martinez CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on: 348951
Blocks:
  Show dependency tree
 
Reported: 2011-09-22 15:29 EDT by Roberto Sanchez Herrera CLA
Modified: 2012-02-07 12:19 EST (History)
5 users (show)

See Also:
cbridgha: review+

Attachments
Proposed patch (3.37 KB, patch)
2012-01-26 10:22 EST, Roberto Sanchez Herrera CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roberto Sanchez Herrera CLA 2011-09-22 15:29:40 EDT 
This bug is to commit the code to 3.3.2


+++ This bug was initially created as a clone of Bug #348951 +++

Build Identifier: Build id: 20110324215508

The default output folder in the Dynamic Web Project changes to "build\classes" when the Java Facet is unchecked and checked again. The default output folder should remain as "WebContent\WEB-INF\classes".

Reproducible: Always

Steps to Reproduce:
1. Open the New Dynamic Web Project wizard
2. Click Modify button to open the FacetsConfigurationDialog
3. Unlock the Java Facet. uncheck and check it again.
4. Click OK on the FacetsConfigurationDialog.
5. Click next on the wizard.
6. The default output folder in the Java Config page will appear as build\classes
Comment 1 Roberto Sanchez Herrera CLA 2012-01-26 10:22:22 EST 
Created attachment 210118 [details]
Proposed patch

Same patch than the one used for the original bug, but for 3.3.2 and 3.4
Comment 2 Roberto Sanchez Herrera CLA 2012-01-26 10:28:06 EST 
Just a clarification: this code was already committed to HEAD in the original bug. So this patch is for WTP 3.3.2 only.
Comment 3 Chuck Bridgham CLA 2012-01-26 10:38:37 EST 
approved
Comment 4 Roberto Sanchez Herrera CLA 2012-01-26 10:48:13 EST 
Code committed to R3_3_maintenance for WTP 3.3.2.
Comment 5 Roberto Sanchez Herrera CLA 2012-02-07 12:19:10 EST 
Resolving bug given that the code was committed already