[
https://issues.apache.org/jira/browse/DAFFODIL-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869921#comment-16869921
]
Michael Beckerle commented on DAFFODIL-1638:
--------------------------------------------
No so simple.
Somehow all of what was described in the comment above has stopped working in
Eclipse for me, though it *was* working......
I am still recommending people just leave all XML validation turned off.
> Isolate invalid DFDL schema and XML files so IDEs dont flag them
> ----------------------------------------------------------------
>
> Key: DAFFODIL-1638
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1638
> Project: Daffodil
> Issue Type: Improvement
> Components: Clean Ups, Infrastructure
> Reporter: Michael Beckerle
> Priority: Major
>
> our daffodil source tree has, intentionally, invalid DFDL schema files that
> cause validation to fail for unit test purposes (negative tests). We should
> rename these files so they don't cause the Eclipse (or other) IDE to create
> distracting validation warnings when you have the daffodil source tree open.
> These tests need to explicitly use file names like foo.dfdl.xsd.invalid so
> that the IDE will not view it as a XSD file and try to validate it.
> This will enable a single setup of Eclipse to be used by persons trying to
> author DFDL schemas, who want the XML & XSD validation capabilities turned
> on, and used by persons trying to do daffodil development.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
