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/10/26 07:13:58 UTC

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

Konrad Windszus created SLING-6188:
--------------------------------------

             Summary: 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


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
(v6.3.4#6332)