Hi Claude, Am 03.05.24 um 07:26 schrieb Claude Warren:
<resource name='src/test/resources/elements/dummy.jar' type='ARCHIVE'/>" This proposal would, in cases where licenses are discovered, add the license entries as with STANDARD resource types. For example: <resource name='src/test/resources/elements/dummy.jar' type='ARCHIVE'>" <license approval="true" family="MIT " id="MIT" name="The MIT License"/> <license approval="true" family="AL " id="AL" name="Apache License Version 2.0"/> </resource>
how would the report on System.out look like?
a) "exploded"
A Foo.jar
GPL3 GPL3 GNU General Public License, version 3
S src/test/java/foo/bar/MyClientTest.java
GPL3 GPL3 GNU General Public License, version 3
S src/test/java/foo/bar/YourClientTest.java
GPL3 GPL3 GNU General Public License, version 3
b) hierarchy?
A Foo.jar
GPL3 GPL3 GNU General Public License, version 3
S Foo.jar://src/test/java/foo/bar/MyClientTest.java
GPL3 GPL3 GNU General Public License, version 3
or with with indentation
S src/test/java/foo/bar/YourClientTest.java
GPL3 GPL3 GNU General Public License, version 3
<snip>
Thoughts?
I like the proposed way to handle archives - if this is documented for our users it's a great way forward and a meaningful extension to RAT.
Thanks for looking into the issue! Cheers, Phil
OpenPGP_signature.asc
Description: OpenPGP digital signature
