Hi *.
Am 15.07.2013 23:01, schrieb Robert Burrell Donkin:
>> Apart from the stuff you mentioned I'd prefer to inject the
>> configuration as well to not pollute pom.xml files with that - currently
>> it's quite a pain to use the tool since you have to configure rat twice.
>
> So, some sort of descriptor...? Perhaps in the project...?
I thought of a very short desciptor (JSON or XML) that just defines the
target licence.
Each licence needs to have a key/implementation class pair so that a
configuration may look like that:
rat-config.json
{
"rat-config": {
"licence": "GPL3",
"implementation": "org.apache.foo.GPL3Licence.java",
"level": "ERROR"
}
}
level could be ERROR / MESSAGE / REPORT meaning that either a message is
just printed, a report file is generated or the build is broken.
One could try to make implementation optional and guess the correct
implementation by matching it magically to the list of available
licences (currently the static variables, that may be changed into
enumerations of all supported licences).
Just a sketch without thinking about implemenation details ;-)
Phil
