|Re: Error-markers for write-protected files [message #665301 is a reply to message #665232]
||Thu, 14 April 2011 08:20
| Sebastian Zarnekow
Registered: July 2009
please file a ticket and attach the use case there.
You could replace the builder module and substitute the MarkerUpdater
with an own implementation that does not ignore read only files. There
is an extension point that allows to enhance the guice module that is
used to instantiate the central components of Xtext. However, it may
only be used once in an Eclipse environment. That is, no other installed
language would be allowed to replace this module. Would that be feasable
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 13.04.11 21:43, schrieb Johannes Stelzer:
> Sebastian Zarnekow wrote on Wed, 13 April 2011 13:24
>> Hi Johannes,
>> there is no way to override this in a language dependent way. The
>> marker handling is done by the builder which works for all languages.
>> See org.eclipse.xtext.builder.builderState.MarkerUpdaterImpl.
>> Why do you need to validate files that are readonly? Does your VCS
>> mark them as such?
>> Need professional support for Eclipse Modeling?
>> Go visit: http://xtext.itemis.com
>> Am 13.04.11 16:13, schrieb Johannes Stelzer:
>> > It seems xtext 1.0.2 creates error-markers not for write protected
>> > files. (Highlighting and references work)
>> > Is there a way to enable this?
> yes we're using Rational Synergy for SCM - and files that are not
> checked out (means sth. like marked as 'in-work' by the developer) are
Powered by FUDForum
. Page generated in 0.02459 seconds