[
https://issues.apache.org/jira/browse/TIKA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157364#comment-16157364
]
Luis Filipe Nassif commented on TIKA-2460:
------------------------------------------
The patch is missing a null check. Will add together with the unit test.
> Possibility to add custom-mimetypes.xml (and/or also other configuration
> files) from location outside classpath
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TIKA-2460
> URL: https://issues.apache.org/jira/browse/TIKA-2460
> Project: Tika
> Issue Type: Improvement
> Components: mime
> Affects Versions: 1.11
> Reporter: Viorica Visan
> Priority: Minor
> Attachments: TIKA-2460.patch
>
>
> I would like to be able to pass to tika the custom-mimetypes.xml from outside
> classpath, because it is more flexible.
> Our application is based on eclipse/osgi and it's composed of multiple
> plugins/bundles.
> One of these plugins contains also the tika library (almost all settings are
> default)
> We usually provide some configuration, from outside to these plugins.
> And we would like to do the same with tika, because we recently encountered:
> https://issues.apache.org/jira/browse/TIKA-2443 and had to provide a custom
> type to workaround a mismatched detection.
> There might be other potential mismatches and it would be good to give this
> possibility to pass configuration to tika from outside our application. Only
> that for the osgi setup, on classpath means inside the folder plugin.
> and from our point of view, that is not a good place, because these plugins
> get replaced at every release, so this patching would have to be maintained
> all the time.
> This is the reason why it would be good, if tika itself had this
> possibility. Thank you.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
