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

ASF GitHub Bot commented on NUTCH-2661:
---------------------------------------

jorgelbg closed pull request #399: NUTCH-2661 Move the TestOutlinks class into 
the o.a.n.parse path
URL: https://github.com/apache/nutch/pull/399
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/src/plugin/index-links/src/test/org/apache/nutch/parse/TestOutlinks.java 
b/src/test/org/apache/nutch/parse/TestOutlinks.java
similarity index 100%
rename from 
src/plugin/index-links/src/test/org/apache/nutch/parse/TestOutlinks.java
rename to src/test/org/apache/nutch/parse/TestOutlinks.java


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Move TestOutlinks to the proper path
> ------------------------------------
>
>                 Key: NUTCH-2661
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2661
>             Project: Nutch
>          Issue Type: Improvement
>            Reporter: Jorge Luis Betancourt Gonzalez
>            Assignee: Jorge Luis Betancourt Gonzalez
>            Priority: Trivial
>             Fix For: 1.16
>
>
> Initially, I placed the {{TestOutlinks}} class in the index-links plugin, 
> although this was when I found the bug with the {{hashCode}}. Now I realised 
> that this test is best to have in the {{test/org/apache/nutch/nutch/parse}} 
> directory. 
> Even more because since this test is not covering any plugin-specific code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to