[jira] [Resolved] (ANY23-87) Bogus arguement in o.a.a.cli.CrawlerTest

["Michele Mostarda (JIRA)" <ji...@apache.org>]

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

Michele Mostarda resolved ANY23-87.
-----------------------------------

    Resolution: Invalid

The Crawler tool extends the Rover tool inheriting all the base class options included the "-f" option. So the test CLI string is correct.

If I misunderstood the issue please reopen it.

 
                
> Bogus arguement in o.a.a.cli.CrawlerTest
> ----------------------------------------
>
>                 Key: ANY23-87
>                 URL: https://issues.apache.org/jira/browse/ANY23-87
>             Project: Apache Any23
>          Issue Type: Bug
>          Components: basic-crawler, CLI
>    Affects Versions: 0.7.0
>            Reporter: Lewis John McGibbney
>            Priority: Critical
>             Fix For: 0.7.0
>
>
> I'm hoping that this is the bug that is buggering up the testCLI. From what I can see in the above class
> {code}
> 61 	ToolRunner.main(
> 62 	String.format(
> 63 	"crawler -f nquads --maxpages 50 --maxdepth 1 --politenessdelay 500 -o %s " +
> 64 	"http://eventiesagre.it/",
> 65 	outFile.getAbsolutePath()
> 66 	).split(" ")
> {code}
> There is no such option/switch on the crawler CLI for a -f parameter, therefore based on the hardcoded nature of the test, at no stage does the crawler become aware of the .nq logic. We could overcome this by changing the logic in line 91 of the same class to use RDFUtils.getRDFParser() instead.
> This however does not address the point that we have either a bogus or else missing CLI parameter which should define the type of document we are trying to fetch.
> On the other hand, please excuse me if this is a wrong assumption altogether as it's been a long day and I'm calling it to a close just now. However I hope this is not the case...

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