[
https://issues.apache.org/jira/browse/CLEREZZA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070533#comment-13070533
]
Fabian Christ commented on CLEREZZA-616:
----------------------------------------
If you use the Apache parent POM this becomes really easy. Use this as the
parent of the Clerezza parent:
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>9</version>
<relativePath />
</parent>
The Apache parent POM defines the "apache-release" profile which automatically
creates standard correct NOTICE and LICENSE files. The "apache-release" profile
is automatically triggered when you use the Maven release plugin with `mvn
release:prepare` and so on.
> Fix incorrect NOTICE files
> --------------------------
>
> Key: CLEREZZA-616
> URL: https://issues.apache.org/jira/browse/CLEREZZA-616
> Project: Clerezza
> Issue Type: Task
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> According to http://www.apache.org/legal/src-headers.html all NOTICE.txt
> files should start with
> Apache Clerezza
> Copyright [yyyy] The Apache Software Foundation
> This product includes software developed at
> The Apache Software Foundation (http://www.apache.org/).
> Which is not the case for a number of them in Clerezza: a number of
> NOTICE.txt files are empty, and others contains text like "Portions are"
> which doesn't say what they are, or "Portions are! Inc. All rights reserved."
> Assuming the top-level NOTICE.txt is ok, this command finds the ones which
> are different:
> md5 $(find . -name NOTICE.txt) | grep -v $(md5 -q NOTICE.txt)
> And the empty ones:
> find . -name NOTICE.txt -size 0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
