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

Sqoop QA bot commented on SQOOP-1247:
-------------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12616996/SQOOP-1247.patch 
against branch sqoop2.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} Patch does not add/modifny any test case
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All tests passed

Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/204/console

This message is automatically generated.

> Sqoop2: Distribution module is missing dependency on Tomcat module
> ------------------------------------------------------------------
>
>                 Key: SQOOP-1247
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1247
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.3
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>            Priority: Blocker
>             Fix For: 1.99.4
>
>         Attachments: SQOOP-1247.patch
>
>
> Binary packaging build has started failing after committing SQOOP-1232. The 
> problem seems to be in the order the modules are built:
> {code}
> [INFO] Sqoop Distribution ................................ FAILURE [27.344s]
> [INFO] Sqoop Integration Tests ........................... SKIPPED
> [INFO] Sqoop Tomcat additions ............................ SKIPPED
> {code}
> The distribution module is built before the Tomcat module, but that should 
> not be the case as the distribution module do have a dependency on tomcat 
> module. It seems that I've missed adding this dependency to the pom files 
> when working on SQOOP-1232. From whatever reason maven used different order 
> for building the modules at that time and as a result this has slipped me. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to