qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Gazzarini <a.gazzar...@gmail.com>
Subject Re: Dependencies license question
Date Mon, 02 Feb 2009 09:41:01 GMT
Sorry there was only "one" question...

Andrea

2009/2/2 Andrea Gazzarini <a.gazzarini@gmail.com>

> Hi Marnie, thanks for reply. Just two questions :
>
> "add details of each additional license to the license file in svn (they're
> separated by language)
> We used to store a license file alongside the jars but it looks like we
> abandoned than in favour of one big license file (correct me here if I'm
> wrong all !!) that lists every license we need per language."
>
> > Where's that file? I saw a LICENSE file under the java folder but it is
> the Apache License; Previously (for Apache Muse stuff) I inserted license
> information
> only into the NOTICE file.
>
> Regards,
> Andrea
>
> 2009/2/2 Marnie McCormack <marnie.mccormack@googlemail.com>
>
> Hi Andrea,
>>
>> If we distribute (or store in our repo) any licensed artifact, then we
>> (sadly) have to take on the responsibility of dealing with it. Most likely
>> the licenses are ok to use (since Jetty is also Apace licensed) but you'll
>> have to check each one and include it as appropriate for Qpid. Basically,
>> if
>> we use it then we have to check out/declare the license for it ourselves.
>>
>> This link gives some useful info on dealing with 3rd party licenses:
>>
>> http://www.apache.org/legal/resolved.html
>>
>> Fundamentally, assuming you want to use/include something with an
>> acceptable
>> non-Apache license then you need to:
>>
>> - add details of each additional license to the license file in svn
>> (they're
>> separated by language)
>> - add details to and notice files in svn (ditto)
>>
>> We used to store a license file alongside the jars but it looks like we
>> abandoned than in favour of one big license file (correct me here if I'm
>> wrong all !!) that lists every license we need per language.
>>
>> This is so that the license is correctly declared/handled. Often the
>> license
>> will provide some text you can use to describe the product you're using in
>> the notice file.
>>
>> Hth - give me a shout if not !
>>
>> Regards,
>> Marnie
>>
>> On Mon, Feb 2, 2009 at 6:51 AM, Andrea Gazzarini <a.gazzarini@gmail.com
>> >wrote:
>>
>> > Hi All, I'm going to submit the first version of QMan Admin
>> console.Before
>> > explaining what it is and how it's working I need help about licensing
>> of
>> > included dependencies.
>> > At the moment (I'm referring to the submitted version) QMan is using
>> only
>> > the Jetty runtime libraries
>> >
>> >
>> >   - jetty-6.1.14.jar
>> >   - jetty-util-6.1.14.jar
>> >   - start.jar
>> >
>> >
>> > Note : Jetty is licensed under Apache License 2.0.
>> >
>> > Now, Jetty is shipped with a lot of libraries that you can use depending
>> on
>> > your nedds. Well, for admin console I need JSP support. So, under the
>> Jetty
>> > distribution there's a folder
>> > "JSP 2.1" and from there I used the following libraries :
>> >
>> >
>> >   - core-3.1.1.jar
>> >   - jsp-2.1.jar
>> >   - jsp-api-2.1.jar
>> >
>> >
>> > Now, before of submit the mentioned libraries, I had a look to their
>> > license
>> > and I saw that the only indication about that is found on their
>> > MANIFEST.MF.
>> > There are three different licenses :
>> >
>> >
>> >   - core-3.1.1.jar is licensed under Eclipse Public License Version 1.0
>> >   - jsp-2.1.jar is licensed under "
>> >   https://glassfish.dev.java.net/public/CDDLv1.0.html"
>> >   - jsp-api-2.1.jar is licensed under Apache License 2.0
>> >
>> >   I presume that, since there are part of Jetty, they can be used
>> without
>> >   any problem at all (I'm simply using those classes without any direct
>> or
>> >   indirect changes) but I'm not an expert on this topic so could help me
>> > about
>> >   that?
>> >
>> > Regards,
>> > Andrea
>> >
>>
>
>

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