Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346187 - Inconsistent plugin.xml and MANIFEST.MF generation policies
Summary: Inconsistent plugin.xml and MANIFEST.MF generation policies
Status: CLOSED WONTFIX
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Windows Vista
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-18 01:22 EDT by Ed Willink CLA
Modified: 2012-11-21 05:08 EST (History)
1 user (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 Ed Willink CLA 2011-05-18 01:22:54 EDT 
plugin.xml is not updated by the Xtext builder. This is good and bad.

Good since it is not corrupted. Bad since it may become invalid after addition of some fragment and the user may neglect to cross-copy from plugin.xml_gen. Suggest, a clear warning at the end of the MWE console output listing any declarations that need migration from plugin.xml_gen.

MANIFEST.MF is updated by the Xtext builder. Also good and bad.

Unfortunately, the builder inserts redundant plug-in dependencies, without version bounds for:  org.eclipse.xtext, org.eclipse.xtext.util, org.eclipse.emf.ecore, org.eclipse.emf.common, org.antlr.runtime. For my application these dependencies are exported by a required bundle ensuring version consistency. Suggest, like plugin.xml, generate a MANIFEST.MF_gen and a clear warning at the end of the MWE console output listing any declarations that need migration from MANIFEST.MF_gen.
Comment 1 Sebastian Zarnekow CLA 2011-05-18 01:30:38 EDT 
Ed,

you can set 'mergeManifest' to false on the Generator in your mwe workflow. You won't get a bold warning but manifest.mf_gen.
Comment 2 Sven Efftinge CLA 2012-11-21 05:08:56 EST 
see comment 1