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

Hudson commented on SQOOP-3415:
-------------------------------

SUCCESS: Integrated in Jenkins build Sqoop-hadoop200 #1243 (See 
[https://builds.apache.org/job/Sqoop-hadoop200/1243/])
SQOOP-3415: Fix gradle test+build when clean applied as the first (vasas: 
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=122d1c0b27c0f5e4532f7a23ce016a5c5756321a])
* (edit) build.gradle


> 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)

Reply via email to