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] Resolved: (TIKA-400) netCDF Tika Parser
Date Mon, 12 Apr 2010 16:00:50 GMT

     [ https://issues.apache.org/jira/browse/TIKA-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting resolved TIKA-400.

    Resolution: Fixed

> why does Maven allow external repos to referenced at all then if they want you to just
put all your artifacts into central anyways?

It's useful for example for companies that have their private repositories and never plan
to release their code to the central. But if you're an open source project, then a separate
repository just makes life more difficult for downstream users.

> can we resolve this issue and then open a new one

Sure, re-resolving.

> netCDF Tika Parser
> ------------------
>                 Key: TIKA-400
>                 URL: https://issues.apache.org/jira/browse/TIKA-400
>             Project: Tika
>          Issue Type: New Feature
>          Components: parser
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.8
> Along with TIKA-399, netCDF is also a widely used scientific data format. I'm going to
throw up a Tika parser that can deal with netCDF.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message