Bug 252613 - Define facet versions for the Java EE 6 projects
Summary: Define facet versions for the Java EE 6 projects
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.2 M3   Edit
Assignee: Kaloyan Raev CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard: JavaEE6
Keywords: plan
Depends on:
Blocks: 260839 272014 272016 290039 290040 311556 313368
  Show dependency tree
 
Reported: 2008-10-29 12:28 EDT by Kaloyan Raev CLA
Modified: 2013-02-11 15:10 EST (History)
3 users (show)

See Also:

Attachments
patch (72.71 KB, patch)
2009-01-13 06:57 EST, Kaloyan Raev CLA 		no flags Details | Diff
patch v2 (72.92 KB, patch)
2009-09-28 09:10 EDT, Kaloyan Raev CLA 		no flags Details | Diff
Show Obsolete (1) 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 Kaloyan Raev CLA 2008-10-29 12:28:27 EDT 
Currently we have defined facets only for projects up to the Java EE 5 specification. We should define Java EE 6 version of the facets as a first step of providing basic Java EE 6 support.
Comment 1 Carl Anderson CLA 2008-12-09 16:30:50 EST 
For the first iteration, we should focus on the basic facets.  There is one scenario that is (most likely) beyond the scope of WTP 3.1 - EJB 3.1 support within a Web 3.0 project.
Comment 2 Kaloyan Raev CLA 2009-01-13 06:57:10 EST 
Created attachment 122402 [details]
patch

The following Java EE 6 facets are added:
  - EAR 6.0
  - EJB 3.1
  - Web 3.0
  - JCA 1.6
  - AppClient 6.0

I set the minimum required version of the Java facet to [5.0, because I don't find anything specific that Java EE 6 requires from Java SE 6. 

I changed the code where facet versions are used on lots of places, but only where the logic is trivial and I feel comfortable to change it. 

The XML Schemas for the Java EE 6 deployment descriptors are still not available, therefore Java EE 6 projects are created with Java EE 5 deployment descriptors at the moment. I opened bug 260839 to track these changes.
Comment 3 Kaloyan Raev CLA 2009-01-13 07:06:48 EST 
Committed to HEAD and released to build.
Comment 4 Chuck Bridgham CLA 2009-01-29 11:18:38 EST 
Re-opening this enhancement...  to de-commit from WTP 3.1....

Java EE 6 support won't be ready in the WTP 3.1 timeframe
Comment 5 Kaloyan Raev CLA 2009-01-29 11:25:51 EST 
I am going to remove the code from the HEAD.
Comment 6 Kaloyan Raev CLA 2009-02-02 06:38:14 EST 
The Java EE 6 support has been deferred from the WTP 3.1 plan. 
The change introduced here must be reverted. I have opened bug 263221 to track this.
Comment 7 Kaloyan Raev CLA 2009-09-17 10:51:02 EDT 
I am sorry I missed the time to submit this for M2. I will do it immediately when M3 is open.
Comment 8 Chuck Bridgham CLA 2009-09-21 13:31:31 EDT 
Hi Kaloyan,

Can you update the patch to resolve the changes that have gone since last January?

We are also preparing for M3, and anticipating these changes will go in immediately.

These also contain some Java EE Constants changes that we are also tracking here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=290039
Comment 9 Kaloyan Raev CLA 2009-09-28 09:10:34 EDT 
Created attachment 148229 [details]
patch v2

This patch is up to date to the WTP 3.2 codeline.
Comment 10 Kaloyan Raev CLA 2009-09-28 09:31:28 EDT 
Patch v2 committed to HEAD and released to build.