|Re: [cross-project-issues-dev] Simrel Build Failing|
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.
On 08/03/2018 15:52, Ed Merks wrote:
Back to the top