I could live with both 2. and 4. > +1 for *contentparser* and moving it to bundles/jcr (next to contentloader) > as > bundles/commons is for modules not related to Sling/JCR at all. No sure whether bundles/jcr is a good fit either, as only some parser's are specific to the JCR (document XML, FileVault XML), others are not (e.g. JSON). Probably bundles/extension/<modulename> would make most sense. Konrad
> > Regards, > O. > >> stefan >> >> >> [1] >> https://svn.apache.org/repos/asf/sling/trunk/bundles/commons/fscontentparse >> r [2] https://issues.apache.org/jira/browse/SLING-6592
