You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2011/09/05 08:53:09 UTC

[jira] [Commented] (FLUME-758) Test Excludes on maven build doesn't always work.

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

Jonathan Hsieh commented on FLUME-758:
--------------------------------------

HBase didn't include a specific version of surefire in its pom.  It ends up uses surefire v2.5.   Flume had explicitly specified surefire 2.8.1.  Removing the version from surefire version from the Flume pom makes it default to v2.5 as HBase does.  The test exclude now works as desired.

This was unexpected.


> Test Excludes on maven build doesn't always work.
> -------------------------------------------------
>
>                 Key: FLUME-758
>                 URL: https://issues.apache.org/jira/browse/FLUME-758
>             Project: Flume
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: v0.9.5
>            Reporter: Jonathan Hsieh
>             Fix For: v0.9.5
>
>
> FLUME-716 added the ability to exclude and include specific builds by using a test.exclude.pattern and test.include.pattern maven -D arguments.  Exclusion was not working properly.  This should get fixed so that we can exclude multiple tests by adding a 
> '-Dtest.exclude.pattern=**/TestFlakyTest.java,**/TestFlakyTest2.java' style command line argument.

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