[
https://issues.apache.org/jira/browse/SLING-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677941#comment-15677941
]
Robert Munteanu edited comment on SLING-6237 at 11/18/16 10:19 PM:
-------------------------------------------------------------------
This change has introduced an unwanted behaviour. In my content projects now I
see the following that javascript and html files are validated as XML.
Reverting [r1767854|https://svn.apache.org/r1767854] fixes the issue for me.
!sling-ide-unexpected-problems.png!
_Edit_: XML, not HTML
was (Author: rombert):
This change has introduced an unwanted behaviour. In my content projects now I
see the following that javascript and html files are validated as HTML.
Reverting [r1767854|https://svn.apache.org/r1767854] fixes the issue for me.
!sling-ide-unexpected-problems.png!
> Reenable XML validator for content package projects
> ---------------------------------------------------
>
> Key: SLING-6237
> URL: https://issues.apache.org/jira/browse/SLING-6237
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.1.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.2.0
>
> Attachments: sling-ide-unexpected-problems.png
>
>
> With SLING-4450 the xml validator was generally disabled for all
> content-package projects. Since the XML validator in general is very useful
> except for the "no grammar defined" warning, we should add a validator based
> on the default XML validator but only ignore missing schemas/DTDs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
