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

Bug 166132

Summary:	Adding other plugin as j2ee module dependency results in META-INF/MANIFEST.MF file in src directory
Product:	[WebTools] WTP Java EE Tools	Reporter:	Martin Taal <mtaal>
Component:	jst.j2ee	Assignee:	jst.j2ee <jst.j2ee-inbox>
Status:	CLOSED INVALID	QA Contact:	Chuck Bridgham <cbridgha>
Severity:	normal
Priority:	P3	CC:	nboldt
Version:	1.0.3
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Martin Taal

2006-11-28 18:02:32 EST

Hi,
When I add another plugin as a J2ee module dependency in my wtp project then it creates a META-INF directory with a MANIFEST.MF file in the referenced project. The MANIFEST.MF file is almost empty and only contains:
Manifest-Version: 1.0
Class-Path: 

My wtp version: 1.1.0.v200606130315/645.

The above causes npe's in build tools (of eclipse.org) as the build tools encounter almost empty manifest.mf files in unexpected locations.

gr. Martin

Comment 1 Nick Boldt

2006-11-28 18:14:11 EST

For more details on the NPE issue in PDE/basebuilder, see bug 166133.

Comment 2 Nick Boldt

2006-11-28 18:16:20 EST

Renaming bug summary slightly. I think the bigger issue is not that the file's almost empty (though that's a problem for PDE), but that it's in the src/ folder instead of in the plugin's root.

Comment 3 Chuck Bridgham

2006-12-13 14:18:13 EST

Checked in WTP 1.3 stream, and only first src directory gets the MANIFEST file.
This is required for J2EE publishing....   Could not reproduce https://bugs.eclipse.org/bugs/show_bug.cgi?id=166133

Comment 4 Chuck Bridgham

2007-03-08 10:02:28 EST

Closing