[
https://issues.apache.org/jira/browse/RAT-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18081506#comment-18081506
]
Philipp Ottlinger commented on RAT-554:
---------------------------------------
At the moment the development in 1.0.0 tries to separate all of the different
RAT UIs from core in order to allow easier integration of new UIs and different
ecosystems (e.g. GitHubActions, Grails Plugin etc.).
Therefore I'd assume that an integration as you imagine it: Maven defining a
configuration for different plugins seems the other way around/an opposite
direction we are going at the moment.
WDYT [~claude]?
> Share ignore information between different RAT tools
> ----------------------------------------------------
>
> Key: RAT-554
> URL: https://issues.apache.org/jira/browse/RAT-554
> Project: Apache RAT
> Issue Type: New Feature
> Reporter: Slawomir Jaranowski
> Priority: Major
>
> We use Maven {{apache-rat-plugin}} to verify project files.
> Some of files in project can be accepted for missing license, like test code,
> simple configurations and so on ....
> To achieve it we use excludes configuration for Maven plugin, so build pass
> with success.
> Configuration for Maven project can be in project root pom, modules pom or in
> external parent pom ... it is inherited in effective pom.
> Next code in project is archived int source artifact.
> Now when I testing ATR (https://release-test.apache.org/) I put such source
> archive to release proces ... and ART which use CLI RAT tool report about
> missing licenses in many files ... configuration from Maven project is not
> used by CLI.
> It will be helpful if different RAT tools like Maven plugin, Ant task, CLI
> can share configuration in some way.
> One proposition which I see is to produce report by RAT maven plugin about
> verification and attach it in source archive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
