[
https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120652#comment-18120652
]
Robert Stupp commented on RAT-163:
----------------------------------
I think https://github.com/eskatos/creadur-rat-gradle is a long-lived and
mature Gradle plugin project.
I am particularly happy to see that it explicitly supports Gradle’s
configuration cache and isolated projects. That is important nowadays, not just
a nice-to-have.
`eskatos/creadur-rat-gradle` has its own focused configuration surface. It
deliberately does not try to expose the complete RAT CLI/user-interface option
surface, including legacy options.
In particular, it does not expose RAT’s source-editing/header-update
functionality.
The existing user base is a significant advantage.
If the maintainer is interested and this is viable, I could imagine exploring a
donation of `eskatos/creadur-rat-gradle` to Apache Creadur RAT.
It could then be iteratively adopted as a RAT UI, gain the wider UI/XML work,
and add a separate explicit Gradle task for source-header updates.
That could give existing users a relatively smooth migration path, potentially
"just" a plugin-ID change.
> 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
> Assignee: Robert Stupp
> Priority: Major
> Fix For: 1.0.0
>
>
> 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)
