[ 
https://issues.apache.org/jira/browse/OPENJPA-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141788#comment-18141788
 ] 

ASF subversion and git services commented on OPENJPA-3069:
----------------------------------------------------------

Commit 2f3510a60f3452dc5139ae2564d38082bfa913ec in openjpa's branch 
refs/heads/OPENJPA-3069 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=2f3510a60 ]

[OPENJPA-3069] Append the module LICENSE and NOTICE parts to the ones of the 
Apache resource bundle

The appended-resources/META-INF/*.vm files replaced the LICENSE and NOTICE
templates of the apache-jar-resource-bundle, so the jars had no Apache
License text and no ASF notice. Plain files are appended instead. The
organization name is now "The Apache Software Foundation" so the copyright
line of the generated NOTICE files has the usual wording.


> Fix license headers, NOTICE and RAT exclusions for the ATR release checks
> -------------------------------------------------------------------------
>
>                 Key: OPENJPA-3069
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-3069
>             Project: OpenJPA
>          Issue Type: Task
>            Reporter: Richard Zowalla
>            Assignee: Richard Zowalla
>            Priority: Major
>             Fix For: 4.2.0
>
>
> Apache Trusted Releases (ATR) checks the release archives with its own rules: 
> it matches the ASF license header word for word, checks the NOTICE wording, 
> and runs RAT with its own defaults, reading exclusions only from a 
> .rat-excludes file at the top of the archive (not from pom.xml).
> On master 74 source files fail the header check (mostly the openbooks example 
> and some test SQL files), the root NOTICE does not have the expected 
> attribution sentence, and there is no .rat-excludes. The source assembly also 
> excludes dot files, so a .rat-excludes would not end up in the source archive.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to