Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330381 - Parent modules should set the same targeted runtime on their children
Summary: Parent modules should set the same targeted runtime on their children
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: 3.2.3   Edit
Assignee: Aidyl Kareh CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-16 12:26 EST by Aidyl Kareh CLA
Modified: 2010-11-18 10:43 EST (History)
3 users (show)

See Also:
cbridgha: review+
jsholl: review+

Attachments
Proposed Patch (11.81 KB, patch)
2010-11-16 12:29 EST, Aidyl Kareh 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 Aidyl Kareh CLA 2010-11-16 12:26:44 EST 
Build Identifier: WTP 3.2.3

When you change the EAR's target runtime, the EAR's child projects get their runtime updated to the same runtime value. However, this new runtime does not cascade down to the child projects mapped into the module projects. When you change the runtime of a Java EE project or of its parent EAR, projects mapped into the Java EE projects should also have their runtime changed to the same value.

Reproducible: Always
Comment 1 Aidyl Kareh CLA 2010-11-16 12:29:53 EST 
Created attachment 183244 [details]
Proposed Patch

This patch modifies the J2EEFacetRuntimeChangedDelegate and EarFacetRuntimeHandler classes so that the runtime changes on Java EE projects are cascaded to child projects.
Comment 2 Chuck Bridgham CLA 2010-11-17 15:03:33 EST 
approve
Comment 3 Jason Sholl CLA 2010-11-18 10:43:56 EST 
Code checked into 32M and HEAD for WTP 3.2.3 and 3.3