Bug 281969 - jst.utility facet should let me choose into which source folder to create MANIFEST.MF
Summary: jst.utility facet should let me choose into which source folder to create MAN...
Status: CLOSED DUPLICATE of bug 349575
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Chuck Bridgham CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-30 04:54 EDT by Thorsten Wärtel CLA
Modified: 2012-09-24 14:06 EDT (History)
2 users (show)

See Also:

Attachments
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 Thorsten Wärtel CLA 2009-06-30 04:54:51 EDT 
Build ID: 20090621-0832

When using m2-eclipse to import a maven project into eclipse, jar-Modules that are depended on by ejb-Modules are given the jst.utility facet.

On installation, this facet creates a default manifest file in the project's first source folder (see org.eclipse.jst.j2ee.project.facet.UtilityFacetInstallDelegate). In a maven project, this is typically the src/main/java folder. As of maven conventions, resource files, like the created manifest, should be placed in a folder src/main/resources, as src/main/java should only contain .java files.

Is it possible to make the folder the manifest is created in configurable, so that a maven project could explicitly request the manifest to be created in src/main/resources ?
Comment 1 Carl Anderson CLA 2009-06-30 16:59:27 EDT 
Assigning to Chuck for initial investigation.
Comment 2 Rob Cernich CLA 2012-09-24 13:25:40 EDT 
Any progress on this?  Importing Maven projects with m2e causes META-INF/MANIFEST.MF to be created in src/main/java.

Also, I believe the facet installer should check to see if the manifest will be generated by Maven.  If so, it shouldn't be creating a manifest at all.
Comment 3 Chuck Bridgham CLA 2012-09-24 14:06:48 EDT 
Handling this as part of work integrating m2e-wtp project.

(BTW - adding this extension to m2e will solve your MANIFEST problem today)

*** This bug has been marked as a duplicate of bug 349575 ***