cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <>
Subject Re: internalizing third-party deps
Date Mon, 30 Aug 2010 08:13:22 GMT
Finally got around to work on pulling this third-party library in our code. So added the Apache
license header to the source files. Now trying to figure out what to do with the original
license / copyright notice. What is our approach to that? Just strip them off the source files
on the premise that they are mentioned in the common NOTICE/LICENSE?

This is what Apache license header seems to imply: "See the NOTICE file distributed with this
work for additional information regarding copyright ownership."

Still wanted to doublecheck.


On Feb 3, 2010, at 8:51 PM, Andrus Adamchik wrote:

> Cool. Thanks for confirming that Justin.
> Cheers,
> Andrus
> On Feb 3, 2010, at 7:12 PM, Justin Erenkrantz wrote:
>> On Wed, Feb 3, 2010 at 9:04 AM, Andrus Adamchik <> wrote:
>>> My current plan is to simply take these parts, put them in Apache Cayenne,
>>> and then make a mention in NOTICE.txt (which is actually already there, as
>>> we've been using it as a third-party lib for ages). Is that enough, or do we
>>> need a code grant from the author to internalize it? (I think we don't as
>>> the code is BSD already)...
>> I think that's enough - there is no need for an explicit grant.  APR
>> imported expat after it was abandoned for a while and we committed our
>> own fixes to it.  (Since then, external expat development has resumed;
>> so we've since taken it back out of the tree.)  -- justin

View raw message