You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@polygene.apache.org by "Paul Merlin (JIRA)" <ji...@apache.org> on 2015/06/13 18:48:00 UTC

[jira] [Commented] (ZEST-27) Integrate RAT into Gradle build.

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

Paul Merlin commented on ZEST-27:
---------------------------------

The `release` task now depends on the `rat` task.
The `rat` task configuration is near the top of the root `build.gradle` file.
The `rat` task itself sits in `gradle/apache-rat.gradle`.

See 22e2008

> Integrate RAT into Gradle build.
> --------------------------------
>
>                 Key: ZEST-27
>                 URL: https://issues.apache.org/jira/browse/ZEST-27
>             Project: Zest
>          Issue Type: Sub-task
>            Reporter: Niclas Hedhman
>
> There is a tool called RAT (http://creadur.apache.org/rat) which checks the codebase for licenses, mainly looking at files to ensure the license headers are in place.
> We should have that being part of the Release task in the Gradle build. Currently, RAT exists for Maven, Ant and command-line, so perhaps we should even contribute something back to Creadur if we get this working.



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