[
https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033679#comment-18033679
]
Philipp Ottlinger commented on RAT-163:
---------------------------------------
[~snazy] no problem - I unassigned the task as Jochen resigned from the Creadur
PMC.
When the first idea of a Gradle plugin came about we had some discussions on
the mailing list and decided not to follow the gradle way as the lifecycle of
these plugins seems totally different from the Maven way. Now that some years
have passed we can easily start an implementation of a Gradle plugin.
Not sure if we should move it to the Creadur PMC or should start it as a forked
side-project and see if it gathers momentum.
Just to give you some more background why the task seems so deserted :) Our
current effort is further harmonizing of all UI's (currently CLI, Maven, Ant),
remove deprecations and publish version 1.0.0 - so any feedback is welcome.
Thanks for your interest in Creadur and in providing a Gradle way to benefit
from RAT!
> Gradle Rat plugin
> -----------------
>
> Key: RAT-163
> URL: https://issues.apache.org/jira/browse/RAT-163
> Project: Apache Rat
> Issue Type: New Feature
> Reporter: David Chen
> Priority: Major
>
> A number of new Apache projects, such as Samza, are using Gradle. However,
> there currently does not exist a Rat plugin for Gradle. The closest
> alternative, the Gradle License Plugin
> (https://github.com/hierynomus/license-gradle-plugin) is not flexible enough
> compared to Rat for use cases such as defining exclusion rules.
> I have created a preliminary Gradle Rat plugin as part of SAMZA-285 and would
> like to clean it up and make it a proper Gradle Rat plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
