Eclipse Community Forums: TMF (Xtext) » How to exclude some specific resource from xtext validation?

Help

Home

Home » Modeling » TMF (Xtext) » How to exclude some specific resource from xtext validation?

Show: Today's Messages :: Show Polls :: Message Navigator

How to exclude some specific resource from xtext validation? [message #1734657]

Fri, 10 June 2016 08:20

Yuwen Hu

Messages: 6
Registered: July 2014

Junior Member

We have our own java validator to validate resource with some fixed suffix.
like *.yam...

But we want to exclude some specific resources from the validator.
like test-*.yam...

How can we customize the xtext validation framework to achieve this?

Report message to a moderator

Re: How to exclude some specific resource from xtext validation? [message #1734658 is a reply to message #1734657]

Fri, 10 June 2016 08:25

Christian Dietrich

Messages: 14665
Registered: July 2009

Senior Member

hi i am note sure "why" you want do do this. and if you really want to stop valiation only
(not parsing, indexing, scoping, ...)

but you may override

org.eclipse.xtext.validation.AbstractInjectableValidator.validate(EClass, EObject, DiagnosticChain, Map<Object, Object>)

and test the EObject's Resource URI

Twitter : @chrdietrich
Blog : https://www.dietrich-it.de

Report message to a moderator

Re: How to exclude some specific resource from xtext validation? [message #1734662 is a reply to message #1734658]

Fri, 10 June 2016 08:35

Yuwen Hu

Messages: 6
Registered: July 2014

Junior Member

Hi Christian,
Thanks for your quickly reply.

Short words for the exclusion reason, our validator checks for our own specific rules. But those rules not applicable for most of the standard resource.
So our target is to only validate the resource which applicable to the specific rules, but exclude all the other resources. (They have the same suffix, so to say).

Any other suggestions to implement our requirement?
Of cause, we can implement filters to filter out specific rules result after validating .
But that cost addition time and cpu to run the validation. So that's not our first choice.

Report message to a moderator