creadur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Burrell Donkin <>
Subject Re: Include Source URLs in Generated LICENSE...?
Date Thu, 01 Nov 2012 20:35:29 GMT
On 11/01/12 14:02, sebb wrote:
> On 1 November 2012 13:16, Chip Childers<>  wrote:
>> On Thu, Nov 1, 2012 at 6:52 AM, sebb<>  wrote:
>>> On 1 November 2012 00:34, Chip Childers<>  wrote:


>>>> Actually, and please do correct me if I don't understand the whisker
>>>> meta-data correctly, we (the CloudStack project) are using the
>>>> "source" attribute to provide a URL from which the reader can access
>>>> the source code of a dependency or included software artifact.  Have I
>>>> misunderstood that attribute?

This is right - the source attribute provides a reference to a location 
where the dependency can be downloaded.


>> The documentation [1] is a little confusing,

Agreed - I've created an issue[2]

>> but as I read it (and the
>> CDDL clause that I believe is being mentioned), I think it's
>> specifically designed to provide a method of linking to the source
>> code.  This isn't important when we are distributing the source
>> itself, but does matter when we are trying to create the legal
>> documents that cover a binary distribution.
>> Given the interpretation above, the reasoning for having the source
>> link in the LICENSE file was specifically for scenarios where there
>> isn't a NOTICE requirement for a particular resource, but we are
>> required to provide a link to the source code.
> OK, in that case I have no objections.

Good :-)

I've been wondering about the right approach to configuration

IMHO the meta-data should be kept separately from configuration-data

For Maven, the plugin configuration would be a natural it. On the 
command line, I lean towards more arguments.



>> [1]


View raw message