[jira] [Resolved] (SIS-60) Duplicated LICENSE and NOTICE files

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SIS-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved SIS-60.
----------------------------------

    Resolution: Fixed
    
> Duplicated LICENSE and NOTICE files
> -----------------------------------
>
>                 Key: SIS-60
>                 URL: https://issues.apache.org/jira/browse/SIS-60
>             Project: Spatial Information Systems
>          Issue Type: Bug
>          Components: Build process
>    Affects Versions: 0.3
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>            Priority: Trivial
>             Fix For: 0.3
>
>
> Execution of {{mvn -Papache-release}} produces a {{sis-0.3-incubating-SNAPSHOT-source-release.zip}} file containing all the project directory with the addition of the following files, which seem auto-generated:
> * LICENSE
> * NOTICE
> * DEPENDENCIES
> The {{LICENSE}} and {{NOTICE}} files are strictly identical to the {{LICENSE.txt}} and {{NOTICE.txt}} files at the root of the project directory, except for the notice header:
> {noformat:title=NOTICE.txt from SVN checkout}
> Apache Spatial Information System (SIS)
> Copyright 2010 The Apache Software Foundation
> {noformat}
> {noformat:title=NOTICE as generated in the sis-0.3-incubating-SNAPSHOT-source-release.zip file}
> Apache SIS
> Copyright 2010-2012 The Apache Software Foundation
> {noformat}
> The {{DEPENDENCIES}} file does not exist in the SVN checkout. There is no GPG signatures or MD5 checksums, but it may be (at least for GPG) because I do not have the necessary keys.
> This result is a file duplication, since the ZIP file contains all of {{LICENSE}}, {{LICENSE.txt}}, {{NOTICE}} and {{NOTICE.txt}} files. The http://apache.org/dev/apply-license.html#new page gives me the feeling that we are supposed to use {{LICENSE}} and {{NOTICE}} filenames without "{{.txt}}" extension. My guess is that the plugin was looking for a {{NOTICE}} file, didn't found it, and consequently generated a default one. The fact that the auto-generated {{NOTICE}} file may be wrong (since it can not contain the project-specific notices) enforces my feeling that this plugin behaviour is just a fallback when no {{NOTICE}} file has been found in the project.
> The proposed action is to rename {{NOTICE.txt}} to {{NOTICE}} and {{LICENSE.txt}} to {{LICENSE}} in the project root directory. The assembly plugin then pickup our files instead than generating default ones.
> Whatever we should also remove the "{{.txt}}" extension in {{CHANGES.txt}}, {{HEADER.txt}} and {{README.txt}} for consistency is an open question.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira