Re: [cross-project-issues-dev] m2e broke indigo
> ... however I have a ton of outgoing changes unrelated to what I have done. ...
> Is that expected? ...
Unfortunately, yes. Sometimes it is due to "end-of-line" issues (bug 325145) and sometimes due to EMF models using generic xml serialization instead of source-maintained xml serialization.
I usually just check in changes I intended, and then "replace from head" to undo all the other little changes due to comments, attribute order, etc. At times, I've tried checking in everything exactly as EMF serialized it, but seems before long contributors have "changed it back".
Pascal Rapicault ---05/13/2011 01:42:05 PM---I just installed the tool and made my change, however I have a ton of outgoing changes unrelated to
From: Pascal Rapicault <pascal@xxxxxxxxxxxx>
To: Eike Stepper <stepper@xxxxxxxxxx>
Cc: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 05/13/2011 01:42 PM
Subject: Re: [cross-project-issues-dev] m2e broke indigo
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
I just installed the tool and made my change, however I have a ton of outgoing changes unrelated to what I have done.
For example I have updates in cdt, dtp, epp, ... contact names moved around in the indigo file.
Is that expected? I'm using org.eclipse.b3.aggregator.editor.feature.feature.group 0.1.0.r01474
On 2011-05-13, at 1:06 PM, Eike Stepper wrote:
> Hi Pascal,
> Sorry, we had to comment out your latest addition to your Indigo contribution file because it broke the build: https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/indigo.runAggregator/409/console
> When you change the structure of your contribution file you should use the EMF editor for that or otherwise make carefully sure that bidirectional references match at both ends.
cross-project-issues-dev mailing list