Tamas Cservenak created RAT-567:
-----------------------------------
Summary: Interoperability improvement; common config file
Key: RAT-567
URL: https://issues.apache.org/jira/browse/RAT-567
Project: Apache RAT
Issue Type: Task
Components: configuration
Reporter: Tamas Cservenak
I did not dig too much into this topic, but right now my pain point is that ASF
Maven build uses RAT w/ project specific configuration "buried" in project POM.
When we release, we use ATR service that also uses RAT but with "own"
configuration, producing a lot of noise.
Reuse of ASF Maven RAT Plugin config, while it is being kept in POM is hard if
not impossible.
Hence, the idea, to implement "common configuration file" for RAT, and all the
integrations like Maven, Ant, Gradle (unsure here does these exist at all or
not) just point RAT at the file, possibly in project root.
As this would then allow to ATR, later on, at release, to agai, pick up ATR
config from source bundle and reuse it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
