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

2024-03-31 Thread Claude Warren
I changed the standard report slightly. It now looks like: s src/test/resources/elements/ILoggerFactory.java MIT MIT The MIT License b src/test/resources/elements/Image.png n src/test/resources/elements/LICENSE n src/test/resources/elements/NOTICE !s

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

2024-03-29 Thread Claude Warren
I have a proposed change. See https://github.com/Claudenw/creadur-rat/pull/6/files Note that this pull request is the difference between multiple targets and the change to move to RAT-366 (Move to single matche call) Example output in

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

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

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