cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <purplecabb...@gmail.com>
Subject Re: Are we supposed to include okhttp source in Cordova-Android?
Date Mon, 29 Apr 2013 18:18:38 GMT
Why was this added? Is it required?

@purplecabbage
risingj.com


On Mon, Apr 29, 2013 at 10:58 AM, Joe Bowser <bowserj@gmail.com> wrote:

> I've updated our NOTICE file indicating that we're using OkHTTP as per
> the Apache Licence.  I think that's good enough, and I noticed the
> headers were not touched, which is good.
>
> Basing it on this: https://www.apache.org/legal/src-headers.html and
> the AOSP Notice File:
> https://android.googlesource.com/platform/frameworks/av/+/jb-dev/NOTICE
>
> On Mon, Apr 29, 2013 at 10:54 AM, Ian Clelland <iclelland@google.com>
> wrote:
> > I'm not a lawyer, and this is not legal advice ;) but OkHTTP is
> > apache-licensed, as is Cordova, and I believe that the terms of the
> Apache
> > license allow us to embed it for distribution.
> >
> > There's probably someone in Apache who is far more qualified than I to
> say
> > what we can and should do, though.
> >
> >
> > On Mon, Apr 29, 2013 at 1:49 PM, Joe Bowser <bowserj@gmail.com> wrote:
> >
> >> Hey
> >>
> >> I saw that okhttp was added, but I don't know if including the source
> >> and as such re-distributing it this way is correct or not.  Is there
> >> someone around to clarify whether it's OK for us to use the library in
> >> this way in the project or not, or whether we have to do what we do
> >> with commons-codec?
> >>
> >> Anyone know the correct answer?
> >>
> >> Joe
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message