Hi Ed
The duplicate ed.merks@xxxxxxxxx is indeed the problem because it
is the no longer unique target for an eOpposite.
I suspect that you got caught out like most happy XML hackers by
thinking that you could do a trivial edit locally. Non-trivial
edits must be done while editing simrel.aggr. The quick validate
build was added to get fast detection of a broken simrel.aggr.
The simrel.aggr + *.aggrcon structure is a good design in that
each project is substantially independent but unfortunately a bad
design in that there are many fragile eOpposites that break if a
project file evolves non-trivially.
I suspect that the simrel.aggr references could all be
unidirectional from *.aggrcon to simrel.aggr and the fragility
would go. The simrel.aggr to *.aggrcon references should be no
more than a contents list of top level elements.
Regards
Ed Willink
On 08/03/2018 15:52, Ed Merks wrote:
Thanks Nick and Arthur for the timely help! I was able to fix
the problem by removing the "EMFT Ecore Tools Build Team"
contact and the reference to it from emft-ecoretools.aggrcon.
Who knew that was a Team?! :-P
I cleaned up the .mailmap file too, whatever that thing is
for...
On 08.03.2018 16:43, Nick Boldt
wrote:
It could be because the simrel.aggr file with
your PR contains your email address TWICE - first on line 538,
and again as added on 659.
I imagine the model might expect every person/email
address is unique, even if they're attached to multiple
projects.
Nick
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
