Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370857 - Utility and web fragment modules are imported with latest version of Java facet, and not with the latest version supported by runtime
Summary: Utility and web fragment modules are imported with latest version of Java fac...
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2.5 P   Edit
Assignee: Roberto Sanchez Herrera CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on: 370780
Blocks:
  Show dependency tree
 
Reported: 2012-02-07 12:35 EST by Roberto Sanchez Herrera CLA
Modified: 2012-02-16 16:30 EST (History)
2 users (show)

See Also:
cbridgha: review+

Attachments
Proposed patch (10.06 KB, patch)
2012-02-07 12:47 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 2012-02-07 12:35:46 EST 
Bug to backport fix to WTP 3.2.5P

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

When a Web, EJB or other modules are imported, the version of the java facet is set to the latest version supported by the target runtime (if a runtime is selected), or to the version appropriate to the Java EE level of the module. But this does not happen for utility or web fragment modules: for those modules, the java facet is always the latest available, which can create a mismatch, for example, if the latest version available for Java is version 1.7, but the target runtime supports up to Java 1.6
Comment 1 Roberto Sanchez Herrera CLA 2012-02-07 12:47:06 EST 
Created attachment 210668 [details]
Proposed patch
Comment 2 Chuck Bridgham CLA 2012-02-07 12:57:20 EST 
approved
Comment 3 Roberto Sanchez Herrera CLA 2012-02-16 16:30:37 EST 
Code committed and released to R3_2_5_patches. Resolving bug