Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 423614

Summary:

Project Explorer metadata content for Java EE 7 projects

Product:

[WebTools] WTP Java EE Tools

Reporter:

Carl Anderson <ccc>

Component:

jst.j2ee

Assignee:

Carl Anderson <ccc>

Status:

RESOLVED FIXED

QA Contact:

Chuck Bridgham <cbridgha>

Severity:

enhancement

Priority:

CC:

cbridgha, ccc, david_williams, dimitar.giormov, kaloyan, naci.dai, neil.hauge, raghunathan.srinivasan, rcuba47

Version:

3.5

Flags:

ccc: pmc_approved? (david_williams)
ccc: pmc_approved? (raghunathan.srinivasan)
ccc: pmc_approved? (naci.dai)
ccc: pmc_approved? (neil.hauge)
cbridgha: pmc_approved+
ccc: pmc_approved? (kaloyan)
cbridgha: review+

Target Milestone:

3.5.2

Hardware:

OS:

Windows Vista

Whiteboard:

JavaEE7 PMC

Bug Depends on:

299747, 400489

Bug Blocks:

Attachments:

Description	Flags
The same patch used for Luna	none

Description Carl Anderson

2013-12-09 12:09:26 EST

This was not covered during initial Java EE 7 work for Kepler.  The support is in Luna, we should put it in Kepler, too.

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

The Java EE 7 project's metadata content is currently not shown in the Project Explorer view. It has to be enabled. 

It is expected that the metadata content for Java EE 5, 6, and 7 projects will work just out-of-the box.

Comment 1 Carl Anderson

2013-12-09 12:11:31 EST

Created attachment 238171 [details]
The same patch used for Luna

This handles the code changes.  The same icons that are used in Luna will be committed separately (as part of this bug).

Comment 2 Carl Anderson

2013-12-09 12:18:08 EST

PMC approval requested to backport a WTP 3.6 enhancement back to WTP 3.5.2.  There are no NLS or API changes.

Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such.

An adopter, IBM, is requesting that this functionality be done for WTP 3.5.2.

Is there a work-around? If so, why do you believe the work-around is insufficient?

There is no workaround to make Java EE 7 projects behave properly in the Project Navigator

How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added?

The Java EE JUnit test bucket has been run.  No JUnits have been added, but this will be tested with every smoke test.  This change is already in WTP 3.6 and is being tested there.

Give a brief technical overview. Who has reviewed this fix?

The WTP Project Navigator contributions have been widened to include the appropriate Java EE 7 levels.  Icons have been added.

What is the risk associated with this fix?

Low risk- this effects the UI presentation of Java EE 7 artifacts, but it is a simple expansion of existing code, and has been well tested.

Comment 3 Chuck Bridgham

2013-12-09 14:05:20 EST

looks good

Comment 4 Carl Anderson

2013-12-13 13:13:09 EST

Committed to R3_5_maintenance for WTP 3.5.2