You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Jukka Zitting (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/07 21:32:29 UTC

[jira] [Resolved] (TIKA-541) Use commons-cli in lieu of writing our own option parser

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

Jukka Zitting resolved TIKA-541.
--------------------------------

    Resolution: Won't Fix

I don't see much benefit to using commons-cli in our case, so resolving as Won't Fix. Please reopen if there's a compelling reason (better features, reduced amount of code, etc.) for why we should use commons-cli.
                
> Use commons-cli in lieu of writing our own option parser
> --------------------------------------------------------
>
>                 Key: TIKA-541
>                 URL: https://issues.apache.org/jira/browse/TIKA-541
>             Project: Tika
>          Issue Type: Improvement
>          Components: cli
>         Environment: All
>            Reporter: Hasan Diwan
>            Priority: Trivial
>         Attachments: tika.pat
>
>   Original Estimate: 0.05h
>  Remaining Estimate: 0.05h
>
> Adds dependency on the commons-cli project -- http://commons.apache.org/proper/commons-cli, version 1.2 -- and rewrites the option parsing code to match that framework.

--
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