Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334156 - Jar with main class in manifest placed in WEB-INF/lib being treated as an application client
Summary: Jar with main class in manifest placed in WEB-INF/lib being treated as an app...
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2.3   Edit
Assignee: Hari Shankar CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-12 14:09 EST by Hari Shankar CLA
Modified: 2011-01-12 23:30 EST (History)
1 user (show)

See Also:
cbridgha: review+

Attachments
patch (1.50 KB, patch)
2011-01-12 14:09 EST, Hari Shankar CLA 		no flags Details | Diff
patch (2.88 KB, patch)
2011-01-12 21:02 EST, Hari Shankar CLA 		ccc: iplog+
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 Hari Shankar CLA 2011-01-12 14:09:23 EST 
Build Identifier: 323

If you place a Jar with main class in manifest placed in WEB-INF/lib of a web project, it is being treated as an application client during deployment. The issue is in the way JavaEEArchiveUtilities figures out whether a class is a plain jar or an app client. 


Reproducible: Always
Comment 1 Hari Shankar CLA 2011-01-12 14:09:47 EST 
Created attachment 186661 [details]
patch

This patch leverages earlier changes made in this area for EAR library feature, to fix the web lib scenario.
Comment 2 Hari Shankar CLA 2011-01-12 21:02:31 EST 
Created attachment 186695 [details]
patch

updated patch
Comment 3 Chuck Bridgham CLA 2011-01-12 22:38:17 EST 
approved
Comment 4 Carl Anderson CLA 2011-01-12 23:30:01 EST 
Committed to R3_2_maintenance and HEAD for WTP 3.2.3 and WTP 3.3 M5