[
https://issues.apache.org/jira/browse/TIKA-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053309#comment-18053309
]
Tim Allison commented on TIKA-4147:
-----------------------------------
Good point. Thank you, [~andreasarf] .
Specifically,
{noformat}
If your MIME-Type needs adding, create a new file
"org/apache/tika/mime/custom-mimetypes.xml" in your codebase.
{noformat}
Should read:
{noformat}
If your MIME-Type needs adding, create a new file "/custom-mimetypes.xml" on
your classpath.
{noformat}
Do we need the initial slash? Is this accurate?
> [JPMS] Alternative way to provide custom MIME types
> ---------------------------------------------------
>
> Key: TIKA-4147
> URL: https://issues.apache.org/jira/browse/TIKA-4147
> Project: Tika
> Issue Type: Improvement
> Components: mime
> Affects Versions: 3.0.0-BETA
> Reporter: Maxim Solodovnik
> Priority: Major
> Fix For: 3.0.0-BETA
>
>
> I'm having src/main/resources/org/apache/tika/mime/custom-mimetypes.xml (As
> recommended here https://tika.apache.org/2.9.0/parser_guide.html)
> But this immediately introduces org.apache.tika.mime package in our jar
> (which is conflicting with same package in Tika ... (( )
> Maybe it worth to create some alternative way to implement this?
> Like
> * Something like MimeTypesFactory.CUSTOM_MIMES_SYS_PROP but pointing to
> resource on classpath?
> * Extendable static Map at MimeTypesFactory?
> * Some sort of Service Locator?
> * something better than above? ))
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
