[
https://issues.apache.org/jira/browse/RAT-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805478#comment-17805478
]
Claude Warren commented on RAT-343:
-----------------------------------
[~romain.manni-bucau] I did not. I stuck with the vanilla Maven code as I am
not normally a Maven plugin developer (this is only the 2nd one I have worked
on). What I would truly love to do is take the XML from the within the
configuration tags and pass that to a process to parse and configure the system.
The internal changes mean that there is one configuration object that every UI
needs to populate. Since the CLI already has the ability to parse XML license
configurations it would be dumb simple to use that parser and have something
that looks the same across both interfaces and the definition file.
> Custom licensenses not working in contrast to v0.15
> ---------------------------------------------------
>
> Key: RAT-343
> URL: https://issues.apache.org/jira/browse/RAT-343
> Project: Apache Rat
> Issue Type: Bug
> Components: license-meta-data, scan, site
> Affects Versions: 0.16
> Reporter: Philipp Ottlinger
> Priority: Major
>
> Due to the changes introduced in 0.16 projects with custom license
> definitions do not seem to work anymore as reported by [~solomax] with
> OpenMeetings:
> [https://github.com/apache/openmeetings/blob/master/pom.xml#L1393]
> Verify that the documentation provided in
> [https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html]
> is correct and ideally add an example usage to
> [CreadurExamples|https://github.com/ottlinger/creadur-rat-examples] to
> prevent future regressions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
