You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Julien Nioche (JIRA)" <ji...@apache.org> on 2014/06/30 16:51:24 UTC

[jira] [Updated] (NUTCH-1804) Move JUnit dependency to test scope

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

Julien Nioche updated NUTCH-1804:
---------------------------------

    Attachment: NUTCH-1804.patch

Patch which : 
* moves JUnit to the test scope
* adds the main test dependencies to the plugins' test classpath
* removes imaginary plugins from list of test targets
* resolve-test task for plugins stores the Ivy dependency in a separate dir for each plugin + add that dir to the test classpath of the plugins

The resolve-test task is not called by the test plugin task as it seems to cause an issue with Tika but none of the plugins use IVY for the test dependencies anyway so things work as they used to after applying the patch.

> Move JUnit dependency to test scope  
> -------------------------------------
>
>                 Key: NUTCH-1804
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1804
>             Project: Nutch
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 1.8
>            Reporter: Julien Nioche
>             Fix For: 1.9
>
>         Attachments: NUTCH-1804.patch
>
>
> Should work straight with core tests after applying [NUTCH-1803] but requires fixing the build for the plugins by either add the main test dependencies to their classpath or force them to declare JUnit as a test dependency in their own ivy.xml. The latter is probably cleaner but we need to make sure that the test dependencies do not get added to the built version of the plugin. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)