Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Message-ID: <13390387.1171332425580.JavaMail.jira@brutus>
Date: Mon, 12 Feb 2007 18:07:05 -0800 (PST)
From: "David Crossley (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Commented: (FOR-855) verify the license situation prior to
 each release
In-Reply-To: <1734237411.1144819399407.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FOR-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472502 ] 

David Crossley commented on FOR-855:
------------------------------------

The ASM license is BSD-style which is an allowed license. See http://www.apache.org/legal/3party.html#category-a

You need to add a copy of their license to tools/ivy/repository/[PROJECTNAME]/LICENSE.txt
(which eventually needs to be declared as per FOR-857).


> verify the license situation prior to each release
> --------------------------------------------------
>
>                 Key: FOR-855
>                 URL: https://issues.apache.org/jira/browse/FOR-855
>             Project: Forrest
>          Issue Type: Bug
>          Components: Project administration
>            Reporter: David Crossley
>         Assigned To: David Crossley
>            Priority: Blocker
>             Fix For: 0.8-dev
>
>
> This should be continually happening anyway, but immediately prior to each release we need to verify that our license situation is in order. This issue should not ever be closed, rather just move the "Fix for Version" on to the next release.
> Here are some of the tasks:
> A) Ensure that all supporting libraries have a corresponding license. Basically every jar file or other external package needs to have a *.license.txt file. Ensure that any license conditions are met, e.g. for some we must add an entry to NOTICE.txt, while for some others we must not. Remember to abide by the ASF guidelines (e.g. nothing more restrictive than the Apache License).
> B) Scan the whole trunk repository to add missing ASF license headers to source files and to ensure that the ASF license headers have not been accidently added to external files. See etc/relicense.txt

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.