guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Jumper (JIRA)" <>
Subject [jira] [Resolved] (GUACAMOLE-133) LICENSE files must include licenses from dependencies
Date Sat, 03 Dec 2016 23:58:58 GMT


Michael Jumper resolved GUACAMOLE-133.
    Resolution: Fixed

> LICENSE files must include licenses from dependencies
> -----------------------------------------------------
>                 Key: GUACAMOLE-133
>                 URL:
>             Project: Guacamole
>          Issue Type: Bug
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Blocker
>             Fix For: 0.9.10-incubating
> From [~gtrasuk] regarding 0.9.10-incubating:
> {quote}
> ... The LICENSE file should include all the licenses that apply, not just the Apache
license.  The idea is to give a downstream user a clear overview of what obligations they’re
taking on.  I believe I’ve seen a “Guide to constructing LICENSE and NOTICE”, but I
don’t have it handy right now.
> {quote}
> (See [the original email in the VOTE thread|])
> The LICENSE/NOTICE document in question is here:
> *This means the LICENSE files will vary by build artifact.* The LICENSE file included
with the source artifacts must include the licenses of all dependencies bundled with the source,
while the LICENSE files included with binary artifacts (like the .war, the various extension
.jars, and the .tar.gz files which contain the extensions) must include the licenses of dependencies
bundled within the binaries/archives.
> Further, according to
> {quote}
> h3. Jars
> * {{META-INF}}
> ** Must include [LICENSE|]
and [NOTICE|]. Note [this|]
> ** Should include a standards compliant MANIFEST. Note [this|].
> {quote}

This message was sent by Atlassian JIRA

View raw message