[
https://issues.apache.org/jira/browse/RAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034756#comment-18034756
]
Claude Warren commented on RAT-163:
-----------------------------------
I have posted a design proposal that spells out what changes should go into
0.18 and what into 1.0.0. This change I listed for 0.18 However, I think it
begs the question monolithic deployment with all the UI components. I think we
need to look at how to split them out into separate components with their own
release cadence. Please take a look at the proposal, perhaps join the mailing
list, and let's have a conversation about how UIs should plug into RAT.
[1] [https://lists.apache.org/thread/5d9cx2wzll2h0g7y9sybp68m7whxcd9h]
> 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)
