[
https://issues.apache.org/jira/browse/SLING-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628132#comment-15628132
]
Konrad Windszus edited comment on SLING-6188 at 11/2/16 8:17 AM:
-----------------------------------------------------------------
Maybe a module validator is the right choice here. That one should be called
only prior to publishing (still to be verified). There would be the right place
to do that kind of validation.
was (Author: kwin):
Maybe a module validator
(https://eclipse.org/webtools/wst/components/validation/scenarios/validation_framework_testplan.html)
is the right choice here, because it is only being executed once during the
build.
> 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
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> 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)
