etch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Veith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ETCH-259) Make JUnit version in build configurable
Date Thu, 14 Feb 2013 21:55:12 GMT

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

Martin Veith commented on ETCH-259:
-----------------------------------

The JUnit version can be configured already in the build process by setting the respective
path to the JUnit jar in the Ant property file "build.dependencies" located at root level.
At the moment we can not upgrade to a newer JUnit version due to a API breach in JUnit. Therefore
we have to adapt our JUnit test cases.
                
> Make JUnit version in build configurable
> ----------------------------------------
>
>                 Key: ETCH-259
>                 URL: https://issues.apache.org/jira/browse/ETCH-259
>             Project: Etch
>          Issue Type: Improvement
>          Components: general
>            Reporter: Paul Turner
>            Priority: Minor
>             Fix For: 1.4
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The JUnit version should be configurable in the build and not hard wired (suggested by
Martin)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message