|
Re: strange behavior in error marker generation [message #1269072 is a reply to message #1268346] |
Tue, 11 March 2014 10:40 |
Sven Efftinge Messages: 1823 Registered: July 2009 |
Senior Member |
|
|
Yes, this is expected.
You need to provide a special implmentation of your
ResourceDecriptionManager's isAffected method, such that the builder
knows that it has to rebuild file1, due to the changes in file2.
Sven
Am 10/03/14 12:35, schrieb Lorenzo Bettini:
> Hi
>
> I've just noted a strange behavior in error marker generation with some
> DSLs (not Xbase based), when more than one file is involved.
>
> Say that file1 uses something from file2; now you change something in
> file2 and save it; file1 is not valid anymore (due to the change in
> file2); well, if you have an open editor on file1, the editor correctly
> shows the error marker, but you have no error marker on file1 in the
> project explorer (nor in the problem view); of course if you modify
> file1 (even with a space) and save it, the error marker now appears in
> the project explorer (and error view).
>
> Is this the expected behavior?
>
> thanks in advance
> Lorenzo
>
--
Need professional support for Xtext or other Eclipse Modeling technologies?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : http://blog.efftinge.de
|
|
|
Powered by
FUDForum. Page generated in 0.03212 seconds