tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-811) Upgrade metadatExtractor version for OpenJDK 7 support
Date Sat, 30 Jun 2012 10:49:44 GMT

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

Jukka Zitting commented on TIKA-811:
------------------------------------

See http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/
for why we want to avoid using other repositories than the central one.

To make it possible for Tika to upgrade to a more recent version of metadata-extractor, you
should work with the upstream project to get their latest releases uploaded to the central
repository. See https://support.sonatype.com/entries/20914616-how-do-i-get-my-software-into-central
for pointers on how to do that. It might even be possible to set up an automatic sync from
the silverpeas repository to the central one.
                
> Upgrade metadatExtractor version for OpenJDK 7 support
> ------------------------------------------------------
>
>                 Key: TIKA-811
>                 URL: https://issues.apache.org/jira/browse/TIKA-811
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.0, 1.1
>         Environment: OpenJDK 7
>            Reporter: Emmanuel Hugonnet
>              Labels: patch, upgrade
>         Attachments: metadata.diff
>
>
> The metadataextractor library (2.4.0-beta-1) is quite old and is depending on some Sun
classes thus making it unable to run on openJDK 7 which is now the default JDK on Linux distributions.
> Upgrading the library to the new version 2.5.0-RC3 fixes this issue but the API has changed.
> Appending a patch to the MetadataExtactor class (and the tests) to take advantage of
this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message