[PR] Bump commons-io:commons-io from 2.15.1 to 2.16.0 [creadur-whisker]

2024-03-28 Thread via GitHub
dependabot[bot] opened a new pull request, #136: URL: https://github.com/apache/creadur-whisker/pull/136 Bumps commons-io:commons-io from 2.15.1 to 2.16.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=commons

[PR] Bump commons-io:commons-io from 2.15.1 to 2.16.0 [creadur-rat]

2024-03-28 Thread via GitHub
dependabot[bot] opened a new pull request, #231: URL: https://github.com/apache/creadur-rat/pull/231 Bumps commons-io:commons-io from 2.15.1 to 2.16.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=commons-io:

RAT-355 (not to be confused with RAT-366)

2024-03-28 Thread Claude Warren
RAT-355 started as a way to dump the running configuration so users could verify what they have configured. This led to the necessity of being able to dump the license definitions. This is the second iteration of the code and uses an annotation to describe the components (Licenses and Matchers).

Re: RAT-366 uncovers an existing issue / Discuss solution

2024-03-28 Thread Claude Warren
SPDX[1] has an interesting format where they can report 2 (or more?) licenses in one. There are a couple of things here that we will need to look at: 1. Metadata only stores one matching license. 2. Can we modify the output XML to list multiple licenses for a file without too much troubl

Re: RAT-366 uncovers an existing issue / Discuss solution

2024-03-28 Thread P. Ottlinger
Hi, Am 28.03.24 um 09:41 schrieb Claude Warren: I got back to looking at 366 and discovered a problem that I think has been lurking in the system for some time. Basically, if a file has the signatures for more than one license only one will be reported, and the selection of which one is (I thin

RAT-366 uncovers an existing issue / Discuss solution

2024-03-28 Thread Claude Warren
I got back to looking at 366 and discovered a problem that I think has been lurking in the system for some time. Basically, if a file has the signatures for more than one license only one will be reported, and the selection of which one is (I think) random. The CI build for RAT-366 shows a test f