You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jeremy Anderson (JIRA)" <ji...@apache.org> on 2011/09/16 17:22:08 UTC
[jira] [Created] (TIKA-716) Upgrade apache-Mime4J to Version 0.7
Upgrade apache-Mime4J to Version 0.7
------------------------------------
Key: TIKA-716
URL: https://issues.apache.org/jira/browse/TIKA-716
Project: Tika
Issue Type: Wish
Components: packaging, parser
Affects Versions: 0.9
Reporter: Jeremy Anderson
Priority: Minor
A newer version of mim4j was released in July 2011.
http://james.apache.org/newsarchive.html#a25072011
It appears it has some imporved functionality for handling various malformed RFC822 messages. Not sure how seemlessly it will intergrate with Tika and other mods.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TIKA-716) Upgrade apache-Mime4J to Version 0.7
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-716.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.10
Assignee: Jukka Zitting
Done in revision 1173421.
> Upgrade apache-Mime4J to Version 0.7
> ------------------------------------
>
> Key: TIKA-716
> URL: https://issues.apache.org/jira/browse/TIKA-716
> Project: Tika
> Issue Type: Wish
> Components: packaging, parser
> Affects Versions: 0.9
> Reporter: Jeremy Anderson
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 0.10
>
>
> A newer version of mim4j was released in July 2011.
> http://james.apache.org/newsarchive.html#a25072011
> It appears it has some imporved functionality for handling various malformed RFC822 messages. Not sure how seemlessly it will intergrate with Tika and other mods.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira