You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/30 02:09:00 UTC

[jira] [Commented] (SQOOP-3415) Fix gradle test+build when clean applied as the first command + warning issue fixes

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

ASF GitHub Bot commented on SQOOP-3415:
---------------------------------------

GitHub user maugly24 opened a pull request:

    https://github.com/apache/sqoop/pull/61

    SQOOP-3415: Fixing gradle clean unittest and gradle warning issues

    (Attila Szabo)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/maugly24/sqoop SQOOP-3415

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sqoop/pull/61.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #61
    
----
commit 12d1484f1f5da030331e3ccbe74b3d0ffff5ad64
Author: Attila Szabo <ma...@...>
Date:   2018-11-30T01:58:59Z

    SQOOP-3415: Fixing gradle clean unittest and gradle warning issues
    
    (Attila Szabo)

----


> Fix gradle test+build when clean applied as the first command + warning issue fixes
> -----------------------------------------------------------------------------------
>
>                 Key: SQOOP-3415
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3415
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Attila Szabo
>            Assignee: Attila Szabo
>            Priority: Major
>             Fix For: 1.5.0
>
>
> If the user wants to build like the following command:
> gradlew clean unittest
> the gradle process ends up in an exception and the whole process left there hanging forever. The root cause of this is the following:
> tasks.withType runs in the configuration part of the build, where we ensure the neccessary directories exist.
> after that clean is executed and all of the dirs got deleted.
> Proposed fix:
> Apply directory creation as the first step of test tasks.
> on the top:
> there are some missing options b/c of Junit annotation processors, and also Xlint information are swallowed currently. We aim to fix these things as well



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)