[
https://issues.apache.org/jira/browse/TIKA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158925#comment-16158925
]
Hudson commented on TIKA-2460:
------------------------------
SUCCESS: Integrated in Jenkins build Tika-trunk #1360 (See
[https://builds.apache.org/job/Tika-trunk/1360/])
TIKA-2460: load custom mimetypes XML from sys prop (lfcnassif:
[https://github.com/apache/tika/commit/70ca280f11fe4127df290b8027c6bc1d5180271f])
* (edit) tika-core/src/main/java/org/apache/tika/mime/MimeTypesFactory.java
* (edit) CHANGES.txt
* (edit) tika-core/src/test/java/org/apache/tika/mime/MimeTypesReaderTest.java
* (add) tika-core/src/test/resources/org/apache/tika/mime/external-mimetypes.xml
> 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, 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)
