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

Bug 425424

Summary:	EMF codegenerator adds plugin to its own dependencies and reexports it
Product:	[Modeling] EMF	Reporter:	Jan Koehnlein <jan>
Component:	Core	Assignee:	Ed Merks <Ed.Merks>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	tom.schindl
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:

Description Jan Koehnlein

2014-01-10 11:52:32 EST

If I have two Ecore models A and B, where B refers to A and both are contained in the same plugin and have separate genmodels in there. When I generate the code for B, it will automatically add a dependency to the plug-in itself in the manifest and even reexport that. This is not only strange but also causes problems in some build systems.

Comment 1 Ed Merks

2014-01-10 13:09:08 EST

This sounds problematic in the first place.  Why do they have two separate GenModels?  There should be just one.  E.g., if each specifies an activator there can't be two of those either.

Comment 2 Ed Merks

2014-01-13 08:05:09 EST

I'm not inclined to fix this.  There should be one GenModel for a project otherwise things like the plugin ID, activator, and so on, can conflict.  The particular issue of this bugzilla is just one example of such a conflict. If you feel compelled to keep it that way, configure B to not to update the classpath.

Comment 3 Jan Koehnlein

2014-01-14 08:56:39 EST

Thanks for clarifying.

Comment 4 Ed Merks

2015-04-09 04:37:10 EDT

*** Bug 464245 has been marked as a duplicate of this bug. ***