Re: svn commit: r1656394 - in /jackrabbit/oak/trunk/oak-lucene/src: main/java/org/apache/jackrabbit/oak/plugins/index/lucene/ test/java/org/apache/jackrabbit/oak/plugins/index/lucene/

Thanks! On Mon, Feb 2, 2015 at 10:37 AM, Chetan Mehrotra wrote: > Hi Julian, > > On Mon, Feb 2, 2015 at 2:17 PM, Julian Sedding wrote: >> Would it not make sense to give the configuration node an extension, >> i.e. tika/config.xml (tika/config.xml/jcr:content/@jcr:data)? > > Makes sense!. Done w

Re: svn commit: r1656394 - in /jackrabbit/oak/trunk/oak-lucene/src: main/java/org/apache/jackrabbit/oak/plugins/index/lucene/ test/java/org/apache/jackrabbit/oak/plugins/index/lucene/

Hi Julian, On Mon, Feb 2, 2015 at 2:17 PM, Julian Sedding wrote: > Would it not make sense to give the configuration node an extension, > i.e. tika/config.xml (tika/config.xml/jcr:content/@jcr:data)? Makes sense!. Done with http://svn.apache.org/r1656425 Chetan Mehrotra

Re: svn commit: r1656394 - in /jackrabbit/oak/trunk/oak-lucene/src: main/java/org/apache/jackrabbit/oak/plugins/index/lucene/ test/java/org/apache/jackrabbit/oak/plugins/index/lucene/

Hi Chetan Would it not make sense to give the configuration node an extension, i.e. tika/config.xml (tika/config.xml/jcr:content/@jcr:data)? That way tika configs that are edited via WebDAV (or installed as part of a content-package) could benefit from the XML support of text-editors. Regards Ju