You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2009/05/23 18:53:45 UTC

[jira] Commented: (TIKA-234) Drop SpellCheckedMetadata

    [ https://issues.apache.org/jira/browse/TIKA-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712443#action_12712443 ] 

Chris A. Mattmann commented on TIKA-234:
----------------------------------------

Hey Jukka,

SpellCheckedMetadata was from Nutch. The goal was to solve the problem with web servers returning: 

CoNtEnT-Type; or
Content-type; or
or CONTENT-TYPE
 
and other problems like that with met keys, where we all wanted them to be the same key, Content-type. I'm not sure there's a huge use case generally for this in Tika, so I'm happy to move this code back to Nutch as a dependency on Tika, depending on what others think. Sami, I know had some contributions to it, so it's probably good to ask him too.

Cheers,
Chris


> Drop SpellCheckedMetadata
> -------------------------
>
>                 Key: TIKA-234
>                 URL: https://issues.apache.org/jira/browse/TIKA-234
>             Project: Tika
>          Issue Type: Improvement
>          Components: metadata
>            Reporter: Jukka Zitting
>            Priority: Minor
>
> There is no clear use case for the SpellCheckedMetadata class, and it's the only case where the commons-lang dependency is used. Nobody on the mailing list seems to be using the class, so I propose that we remove it as obsolete to get rid of the commons-lang dependency.

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