Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-6188

Improve validators

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • Sling Eclipse IDE 1.1.0
    • Sling Eclipse IDE 2.0.0
    • IDE
    • None

    Description

      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.

      Attachments

        Issue Links

          is related to

          Test - A new unit, integration or system test. SLING-4031 Missing MANIFEST.MF should be a validation error

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. SLING-4070 Validation errors are not cleared

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              kwin Konrad Windszus
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: