[
https://issues.apache.org/jira/browse/SQOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236340#comment-14236340
]
Sqoop QA bot commented on SQOOP-1847:
-------------------------------------
Testing file
[SQOOP-1847.patch|https://issues.apache.org/jira/secure/attachment/12685459/SQOOP-1847.patch]
against branch sqoop2 took 0:20:47.185898.
{color:red}Overall:{color} -1 due to 3 errors
{color:red}ERROR:{color} Patch does not add/modifny any test case
{color:red}ERROR:{color} Some unit tests failed
{color:red}ERROR:{color} Failed unit test:
{{org.apache.sqoop.connector.idf.TestCSVIntermediateDataFormat}}
{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 integration tests passed
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/704/console].
This message is automatically generated.
> Sqoop2: Move rat configuration from special execution to the main execution
> ---------------------------------------------------------------------------
>
> Key: SQOOP-1847
> URL: https://issues.apache.org/jira/browse/SQOOP-1847
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.5
>
> Attachments: SQOOP-1847.patch
>
>
> I would like to add a special step in our pre-commit hook to run the Apache
> RAT to check that given patch doesn't have any files without proper license
> headers. Sadly our current rat configuration puts all the excludes into
> section that is available only when running {{mvn verify}}. As there is no
> other execution profile I think that it will be fine to move that
> configuration as the default one, so that {{mvn apache-rat:check}} works the
> same way as calling {{mvn verify}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
