[jira] [Updated] (SLING-6188) Improve validators

["Robert Munteanu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-6188:
-----------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.2.2)
                   Sling Eclipse IDE 1.2.4

> Improve validators
> ------------------
>
>                 Key: SLING-6188
>                 URL: https://issues.apache.org/jira/browse/SLING-6188
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.1.0
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.2.4
>
>
> Both validators being provided by Sling IDE (checking manifest.mf consistency as well as checking for a valid jcr_root) are not classical WST validators bound to a specific file.
> E.g. manifest.mf can become invalid if one of the referenced service.xmls vanishes during the build. So it is hard to tell which modifications require a revalidation. For the content package validation it is currently triggered only once per validation run (still too often) but not filtered on any specific files.
> I would rather propose to not use WST validators for those cases but rather do that check only once after each build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)