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

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

Testing file 
[SQOOP-1966.patch|https://issues.apache.org/jira/secure/attachment/12690733/SQOOP-1966.patch]
 against branch sqoop2 took 0:30:36.200527.

{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} License check passed
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All unit tests passed
{color:green}SUCCESS:{color} All integration tests passed

Console output is available 
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/892/console].

This message is automatically generated.

> Suggest to turn off source distribution profile by default
> ----------------------------------------------------------
>
>                 Key: SQOOP-1966
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1966
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: sqoop2-build
>    Affects Versions: 2.0.0
>            Reporter: Jerry Chen
>            Assignee: Qian Xu
>            Priority: Minor
>         Attachments: SQOOP-1966.patch
>
>
> Currently, when build Sqoop2 with mvn command, "source" profile to build 
> source distribution is activated by default, while the more important profile 
> "binary" for building binary distribution is by default NOT activated. 
> Looking from other Hadoop projects such as Hadoop Common or HDFS, the source 
> profile and dist profile will not activated by default. The default will only 
> perform package building across the projects. This approach makes sense 
> because source distribution doesn't look to be always needed profile and not 
> used so often.



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

Reply via email to