nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NUTCH-1737) Upgrade to recent JUnit 4.x
Date Sat, 29 Mar 2014 21:39:16 GMT

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

Lewis John McGibbney commented on NUTCH-1737:
---------------------------------------------

No probs at all :) The original ticket description is enough to justify this as an important
issue as porting tests between branches is something which has come in handy as of recent.
 

> Upgrade to recent JUnit 4.x
> ---------------------------
>
>                 Key: NUTCH-1737
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1737
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: 1.8
>            Reporter: Sebastian Nagel
>            Assignee: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 1.9
>
>         Attachments: NUTCH-1737-trivial.patch, NUTCH-1737.patch
>
>
> While trunk still remains on JUnit 3.8.1, 2.x uses JUnit 4.11 and has already upgraded
tests (NUTCH-1573). This makes it difficult to port tests which use JUnit 4 features from
2.x to trunk. There are two solutions:
> # (lightweight, trivial patch attached) upgrade only ivy dependency, upgrade tests later
> # upgrade also all tests to use JUnit 4 annotations and setup(), cf. NUTCH-1573



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

Mime
View raw message