My thought here was that there are a number of applications that use custom licenses (Actually they are licenses that we don't have by default). It would be nice if there was a repository of contributed licenses that could be updated at a difference cadence than the core code. There are at least 2 tickets that I know of that were looking for new licenses to be defined. I think that it might encourage more participation.
RAT-373 is looking for specific file types so that we can test the Tika based parser. I don't have those and don't know how to create them. RAT-370 is about creating performance tests so that we can see if we are significantly impacting the run time. For example RAT-46 is asking for a PHP license check. Under this change we would create a PHP.xml file that describes the PHP license(s) and place it in the shared space. Then users who want that license can download the file and add it to the processing as follows: - CLI : --licenses PHP.xml - Maven : in pom <additionalLicenseFiles>PHP.xml</additionalLicenseFiles> (there is not command line option for this but it could be added during harmonization (RAT-323) - Ant: <setLicenses><file file='PHP.xml' /></setLicenses> The advantage I want to try to push is that you define the thing once and can use it with any that supports the core '--licenses' option. I think we can do the same sort of thing with exclusion files. So you can develop an exclusion file that handles any SCCS. Note: for harmonization I want to produce a table of CLI commands and equivalent commands in Maven and Ant. But that takes some harmonization. Claude On Sat, May 11, 2024 at 9:00 PM P. Ottlinger <pottlin...@apache.org> wrote: > Hi Claude, > > Am 11.05.24 um 09:45 schrieb Claude Warren: > > Create a repository for license files separate from the main tool. > Perhaps > > in the tools section, perhaps as a separate git project. The idea is > that > > teams can develop/refine license definitions and release them into a > shared > > space. This will make it easier if someone wants to find the PHP > license > > for example. Then we should put the PHP and EUPL licenses in there. We > > can also put the XSD for license/configuration in there. > > Do you mean this as a solution to > https://issues.apache.org/jira/projects/RAT/issues/RAT-373 and > https://issues.apache.org/jira/projects/RAT/issues/RAT-370 > > OR do you mean this as a release independent way to provide example > definitions of licenses/license combinations/license configurations/RAT > configurations? > > If it is part of a license lexicon I'd prefer it to have a site that we > deploy somewhere. This was the reason for me to start my personal > https://github.com/ottlinger/creadur-rat-examples as I was unable to > understand the Maven plugin's configuration possibilities :) > > Cheers, > Phil > > -- LinkedIn: http://www.linkedin.com/in/claudewarren
