abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James M Snell <jasn...@gmail.com>
Subject Re: JSON license headers
Date Mon, 20 Nov 2006 17:11:32 GMT
Hmm... is there a "not quite 'right' but will still work" solution we
can shoot for in the near term?

- James

Stephen Duncan wrote:
> The "right" solution, I think, is to get a binary release under the
> Apache license published to the central Maven repository, and then it
> could be downloaded for use by Ant or by Maven.
> 
> -Stephen
> 
> On 11/18/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
>> On 11/18/06, James M Snell <jasnell@gmail.com> wrote:
>> > You know, I'm actually wondering if it makes sense for us to have the
>> > json code in our svn.  The source we are using can be downloaded from
>> > http://json.org/java/apache.zip.  Like the other dependencies, we
>> can go
>> > out and grab that as needed during the build.  We can also make it
>> > optional to build.  I also don't think we should be shipping the source
>> > code for it in our source zip.  This will make it just another
>> > dependency rather than such a special case.  It should also make it
>> > possible for us to proceed without having to worry about if/when we can
>> > get the license headers added to these three files.
>> >
>> > thoughts?
>>
>> Well, for the ant build we can certainly download it and build it on
>> the fly, but for maven builds it'll go out and download whatever's in
>> the maven repositories, which wouldn't be under the proper license...
>> Not sure what the "right" solution is to that.
>>
>> -garrett
>>
> 
> 

Mime
View raw message