[
https://issues.apache.org/jira/browse/TIKA-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Burch resolved TIKA-647.
-----------------------------
Resolution: Fixed
Fix Version/s: 1.0
Thanks for spotting that, fixed in r1098891.
> TikaCLI only reports internal meta models with --list-met-models
> ----------------------------------------------------------------
>
> Key: TIKA-647
> URL: https://issues.apache.org/jira/browse/TIKA-647
> Project: Tika
> Issue Type: Bug
> Components: cli
> Affects Versions: 0.8, 0.9, 1.0
> Reporter: Andreas Kemkes
> Fix For: 1.0
>
>
> From TikaCLI.java
> for (Class<?> modelClass: modelClasses) {
> // we don't care about internal Tika met classes
> // if we do, then we can take this conditional out
> if (modelClass.getSimpleName().contains("Tika")) {
> System.out.println(modelClass.getSimpleName());
> The condition is the reverse from what the comment says and needs to be
> negated. The way it's written, it only returns the internal ones.
> java -jar tika-app-0.9.jar --list-met-models
> TikaMetadataKeys
> PROTECTED
> RESOURCE_NAME_KEY
> TikaMimeKeys
> MIME_TYPE_MAGIC
> TIKA_MIME_FILE
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
