You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/11/03 10:03:58 UTC
[jira] [Commented] (SLING-4450) Configure the XML validator to not
run for content projects
[ https://issues.apache.org/jira/browse/SLING-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632268#comment-15632268 ]
Konrad Windszus commented on SLING-4450:
----------------------------------------
The only option to disable the grammar check is by setting {{indicateNoGrammer}} to {{0}} in the project scope of the preference store for the qualifier {{org.eclipse.wst.xml.core}} (compare with {{org.eclipse.wst.xml.core.internal.validation.eclipse.Validator#setupValidation}}). That isn't really nice, because it has to be done for each project individually. Therefore I would prefer to have our own configurator derived from org.eclipse.wst.xml.core.internal.validation.eclipse.Validator which always disables that option. Other than that it should behave exactly as the default XML validator (as configured in project or workspace preferences).
> Configure the XML validator to not run for content projects
> -----------------------------------------------------------
>
> Key: SLING-4450
> URL: https://issues.apache.org/jira/browse/SLING-4450
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.6
>
>
> Currently .content.xml files are validated and trigger spurious warnings about "No grammar constraints (DTD or XML Schema) referenced in the document." .
> There seems to be an extension point for achieving this, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=227834 .
> In the future we could consider providing our own validator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)