Bug 529289 - The Xtext nature/builder provides no file path filtering
Summary: The Xtext nature/builder provides no file path filtering
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.12.0   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-29 05:06 EST by Ed Willink CLA
Modified: 2017-12-29 05:17 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2017-12-29 05:06:59 EST 
The increased validation that occurs as a consequence of EMF EAnnotation validation (Bug 529257) highlights that Xtext provides no way to inhibit validation of *.ecore / DSL files copied to the Maven/Tycho "target" folder. All errors reported against a source file are re-reported against the "target" copy. This is a visual pain in the Problems View and an unnecessary waste of validation time.

The Java nature uses the classpath to filter files and the "target/classes" folder is not on the classpath; no duplicate compilation.

Perhaps the Xtext nature needs to provide included/excluded regexes analoguous to the Java to-bin copy for the classpath.

-  Suggest include/exclude in the xtextBuilder .project buildCommand.

Perhaps an Xtext preference to treat .gitignore as an exclusion

Perhaps support a .xtextignore to define exclusions

Suggest a warning for projects with a pom.xml or ../pom.xml and no exclusion.