thanks for all the feedback - from the discussion i got the following next steps and will take care of them:
1. rename it to "contentparser" 2. move it to bundles/jcr (next to contentloader) *) 3. remove the parse(File) methods from the API 4. think about making a variant of the TestUtil.getDeep() method available in the API as well - it was already duplicated in fsresource *) although contentparser has no other sling deps the filevault format has direct jcr dependency, and even the JSON format parsing has some special logic to make it fit best for serialized JCR content concerning using contentparser in contentloader: konrad already created a ticket https://issues.apache.org/jira/browse/SLING-6634, see discussion there. stefan
