You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/01/03 13:40:58 UTC

[jira] [Resolved] (SLING-4541) Provide an extensive test suite for the JCR content loader

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

Carsten Ziegeler resolved SLING-4541.
-------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: JCR ContentLoader 2.2.0)

> Provide an extensive test suite for the JCR content loader
> ----------------------------------------------------------
>
>                 Key: SLING-4541
>                 URL: https://issues.apache.org/jira/browse/SLING-4541
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR ContentLoader 2.1.10
>            Reporter: Radu Cotescu
>            Assignee: Petr Shypila
>         Attachments: week-4-completed.patch, week-4_first_part.patch, week2-part1-pathentry.patch, week2-part2-defaultcontentcreator.patch, week2-part3-single-jcrmock-test.patch, week3.patch, week4-5.patch
>
>
> The JCR content loader is a sensible bundle. An extensive IT suite should be written to make sure that code changes don't affect core functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)