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

Bug 340803

Summary:

Regular jars are imported as App Client projects when importing an EAR 5.0 or 6.0 if jars have MAIN-CLASS attribute in MANIFEST.MF

Product:

[WebTools] WTP Java EE Tools

Reporter:

Roberto Sanchez Herrera <shr31223>

Component:

jst.j2ee

Assignee:

Roberto Sanchez Herrera <shr31223>

Status:

RESOLVED FIXED

QA Contact:

Chuck Bridgham <cbridgha>

Severity:

normal

Priority:

CC:

ccc

Version:

3.2.3

Flags:

cbridgha: review+

Target Milestone:

3.2.4

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Proposed patch	ccc: iplog+

Description Roberto Sanchez Herrera

2011-03-23 16:26:17 EDT

Build Identifier: WTP 3.2.3

If an EAR version 5 or 6 contains regular jars that have set the MAIN-CLASS attribute in MANIFEST.MF, they are imported as Application client projects when the EAR is imported

Reproducible: Always

Steps to Reproduce:
1. Import an EAR version 5 or 6 that contains contains regular jars that have set the MAIN-CLASS attribute in MANIFEST.MF
2. Note that the jars are imported as Application Client projects
3.

Comment 1 Roberto Sanchez Herrera

2011-03-23 22:51:23 EDT

Created attachment 191801 [details]
Proposed patch

This patch was created using R3_2_maintenance. With this patch, a jar will not be scanned for MAIN-CLASS attribute in MANIFEST.MF if the jar is in the lib directory of an EAR version 5 or 6

Comment 2 Chuck Bridgham

2011-03-30 11:16:30 EDT

approve

Comment 3 Carl Anderson

2011-03-30 21:17:47 EDT

Committed to R3_2_maintenance and HEAD for WTP 3.2.4 and WTP 3.3 M7