[ https://issues.apache.org/jira/browse/FOR-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472463 ]
Ross Gardler commented on FOR-855: ---------------------------------- With the move to Ivy we will no longer have jar files in the lib directory, they will instead be in tools/ivy.repository/[PROJECTNAME]/jars As a result we will no longer need to name license files *.license.txt as they can be placed within the projectname directory. I'm not sure how this affects the related issue FOR-857 I will be performing Part A as I work our dependencies and add them to our ivy repository. I'll post any issues requiring more oversight against this issue. > 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.