Bug 349575 - Add an option to (not) generate the manifest when adding a Facet
Summary: Add an option to (not) generate the manifest when adding a Facet
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.3   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Chuck Bridgham CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard: Maven
Keywords: plan
: 281969 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-16 10:57 EDT by Fred Bricon CLA
Modified: 2014-02-05 15:47 EST (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Bricon CLA 2011-06-16 10:57:42 EDT
Build Identifier: 

I'm working on the m2e/WTP integration plugin. m2e-wtp 0.13.0 now uses maven-generated manifests, as announced here : http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00692.html

Doing so, WTP-generated manifests become irrelevant, so the m2e-wtp plugin tries to guess where they are generated and delete them if necessary. That's the dirty way of getting around WTP.
The proper way would be to add a new DataModel variable that would basically tell WTP to generate the manifest for a project, or not. m2e-wtp would call something like :
IDataModel modelConfig = ....
...
modelConfig.setProperty(IJ2EEModuleFacetInstallDataModelProperties.GENERATE_MANIFEST, false);
..

Default value would be true, to keep existing behaviour 

Reproducible: Always
Comment 1 Rob Stryker CLA 2011-06-17 01:05:57 EDT
Fred:  If you could make a patch, I can definitely help to get it committed and approved, possibly for 3.3.1 if I can get approvals. 

Assuming you don't have the full dev environment to make a patch, if you can at least describe the few classes that changes need to be made in to give me a head start, I can definitely assist you in getting a patch made and committed. 

Ping me if you need help.
Comment 2 Chuck Bridgham CLA 2012-09-24 14:06:48 EDT
*** Bug 281969 has been marked as a duplicate of this bug. ***