sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2478) Sqoop2: Downgrade cobertura plugin to version 2.6
Date Fri, 14 Aug 2015 00:01:45 GMT

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

Hudson commented on SQOOP-2478:
-------------------------------

SUCCESS: Integrated in Sqoop2 #873 (See [https://builds.apache.org/job/Sqoop2/873/])
SQOOP-2478: Sqoop2: Downgrade cobertura plugin to version 2.6 (abe: https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=41fff36672700f9b46f22d1be7c73707d5d7467d)
* pom.xml


> Sqoop2: Downgrade cobertura plugin to version 2.6
> -------------------------------------------------
>
>                 Key: SQOOP-2478
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2478
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.6
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.7
>
>         Attachments: SQOOP-2478.patch
>
>
> Me and [~abec] spent quite a time trying to figure out why our precommit hook started
suddenly executing integration tests as part of unit test phase. We've triaged the problem
to upgrading {{maven-cobertura-plugin}} that happened in SQOOP-2472. Based on the [release
notes|http://blog.soebes.de/blog/2015/03/03/mojo-cobertura-maven-plugin-2-dot-7-released/],
the version 2.7 fixed a "bug":
> * MCOBERTURA-86 – no coverage reported for integration-test
> However fixing this "bug" has introduced breaking of our [workflow|https://xkcd.com/1172/].
I did not find a way how to skip integration tests and hence I would like to propose downgrading
the pluing to version 2.6.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message