[
https://issues.apache.org/jira/browse/NUTCH-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625630#comment-13625630
]
Lewis John McGibbney commented on NUTCH-1555:
---------------------------------------------
I was thinking about using commons cli for better parsing of command line
arguments. Over some time we have had problems with the CLI parsing and using
an established framework like commons cli or jcommander would really clear that
up.
Regarding the String type arguments, I suppose we would need to enforce more
strict type and data checking if we were not to use some framework (here I
assume a CLI framework would provide us with this functionality from the
beginning)
What do you think Feng?
> bug in 2.x ParserJob command line parsing
> ------------------------------------------
>
> Key: NUTCH-1555
> URL: https://issues.apache.org/jira/browse/NUTCH-1555
> Project: Nutch
> Issue Type: Bug
> Components: parser
> Affects Versions: 2.1
> Reporter: Lewis John McGibbney
> Fix For: 2.2
>
>
> I just accidentally passed in the following argument to parser job
> {code}
> law@CEE279Law3-Linux:~/Downloads/asf/2.x/runtime/local$ ./bin/nutch parse
> updatedb
> ParserJob: starting
> ParserJob: resuming: false
> ParserJob: forced reparse: false
> ParserJob: batchId: updatedb
> ParserJob: success
> {code}
> This is a bug for sure
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
