Bugzilla – Full Text Bug Listing
| Summary: | [xtext][validation] Don't create error markers in output folders | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Aaron Digulla <digulla> | ||||
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | karsten.thoms, sebastian.zarnekow | ||||
| Version: | 2.0.0 | Flags: | sebastian.zarnekow:
indigo+
|
||||
| Target Milestone: | SR2 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Aaron Digulla
Fixed by excluding folders that are marked as output folders of java projects. Please note that the derived flag does not seem to be a good indicator for marker creation, e.g. the JDT will produce error markers for derived java files, too. That only solves half of my issue because if have two sets of output folders (one is under control of Eclipse and the other is created by Maven). With your fix, I still get errors in the Maven folders. I'm afraid you have to keep your Eclipse project configuration in sync with your maven settings. Isn't that a good idea anyway? One alternative that comes to my mind would be to have a concept of source folders for each Xtext language which doesn't sound too convenient to me and is not an option. Do you have another idea? The setup is normal if you need to run Maven from the command line as well as from within Eclipse. In that case, you need to tell Maven from the command line to compile into a different folder than Eclipse because otherwise, Eclipse gets really confused. So I have a POM which sets the target folder based on two profiles. In the project properties, there is an entry for "Validation" where you can fine-tune validation for XML, DTDs, etc. But that dialog is so hidden that most users never found it and b) it's so horrible that those who did wish they didn't. But maybe you can add your validation there and allow me to add "ignore folders patterns" for Xtext. Created attachment 203331 [details] Screenshot: Error markers in target/classes (In reply to comment #3) > I'm afraid you have to keep your Eclipse project configuration in sync with > your maven settings. Isn't that a good idea anyway? Depends. If you use Maven "classic" the sources are usually compiled with javac. Tycho uses JDT. When using Tycho, this seems OK for me. The classes are compiled to target/classes, which is also configured as output folder. Then your fix would work. (I'm getting the same annoying validation messages so far, see screenshot) Karsten, which Xtext build do you have installed? Did you mark target as default project output folder and target/classes as output folder for your source path's? (In reply to comment #6) > which Xtext build do you have installed? 2.0.1.v201109090504 > Did you mark target as default project output folder and target/classes as > output folder for your source path's? Oh, it was still /bin! My fault, thought that Maven had configured that to target/classes. (In reply to comment #7) > (In reply to comment #6) > > which Xtext build do you have installed? > 2.0.1.v201109090504 > > > Did you mark target as default project output folder and target/classes as > > output folder for your source path's? > Oh, it was still /bin! My fault, thought that Maven had configured that to > target/classes. Could you please double check if the latest changes in the master branch fix the error marker-issue for you if after you fixed your project setup? Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |