[
https://issues.apache.org/jira/browse/SQOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236409#comment-14236409
]
Hudson commented on SQOOP-1847:
-------------------------------
FAILURE: Integrated in Sqoop2-hadoop100 #711 (See
[https://builds.apache.org/job/Sqoop2-hadoop100/711/])
SQOOP-1847: Sqoop2: Move rat configuration from special execution to the main
execution (abe:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=c0c9b9ef722d047baa8ef719cd24aa6f18315f52)
* pom.xml
> 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)
