commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maurizio Cucchiara (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OGNL-9) Upgrade JUnit to version4
Date Tue, 17 May 2011 21:57:47 GMT

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

Maurizio Cucchiara commented on OGNL-9:
---------------------------------------

Patch applied. 
What's more this behaviour agrees with the api docs:
{code}
/**
     * Finds the best possible match for a method on the specified target class with a matching
name.
     * <p>
     * The name matched will also try different combinations like <code>is + name, has
+ name, get + name, etc..</code>
     * </p>
     * 
     * @param target The class to find a matching method against.
     * @param name The name of the method.
     * @return The most likely matching {@link Method}, or null if none could be found.
     */
{code}    
  

> Upgrade JUnit to version4
> -------------------------
>
>                 Key: OGNL-9
>                 URL: https://issues.apache.org/jira/browse/OGNL-9
>             Project: OGNL (Incubating)
>          Issue Type: Task
>            Reporter: Simone Tripodi
>            Assignee: Simone Tripodi
>         Attachments: OGNL-9-1.patch, ognl-9.patch
>
>
> Actually OGNL is tested using JUnit3; in Commons we've been migrating tests to JUnit4,
as a first step just upgrading the dependency and refactoring the Test classes just by dropping
the TestCase inheritance and using the annotation would be enough (methods refactoring dropping
the 'test' prefix can be postponed).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message