jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2504) Allow indexingConfiguration to be loaded from the classpath
Date Fri, 09 Apr 2010 10:57:51 GMT

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

Jukka Zitting updated JCR-2504:

    Resolution: Fixed
      Assignee: Jukka Zitting
        Status: Resolved  (was: Patch Available)

Committed to trunk in revision 932319 and merged to the 2.1 branch in revision 932348. Thanks!

> Allow indexingConfiguration to be loaded from the classpath
> -----------------------------------------------------------
>                 Key: JCR-2504
>                 URL: https://issues.apache.org/jira/browse/JCR-2504
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: indexing
>    Affects Versions: 1.6.1, 2.0.0
>            Reporter: fabrizio giustina
>            Assignee: Jukka Zitting
>             Fix For: 2.1.0
>         Attachments: indexingConfiguration_classpath.diff
> The "indexingConfiguration" attribute in the SearchIndex configuration (http://wiki.apache.org/jackrabbit/IndexingConfiguration)
actually requires an absolute filesystem path.
> It would be nice if SearchIndex would also accept a file available in the classpath...
although you can use variables like ${wsp.home} or similar there are many scenarios where
a classpath resource would help (for example when creating a new workspace the directory structure
is automatically created by jackrabbit and doesn't need to be already available but the indexing
configuration file does).
> I am attaching a simple patch to SearchIndex that tries to load the file from the classpath
if it has not been found. Since priority is given to the old behavior (file before classpath)
so it's fully backward compatible.
> Diff has been generated against trunk, it would be nice to have this patch also on the
2.0 branch.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message