www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LEGAL-84) What are the requirements for the [PRODUCT_NAME] in the NOTICE file?
Date Sun, 22 Mar 2015 22:13:11 GMT

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

Henri Yandell closed LEGAL-84.
    Resolution: Done

> What are the requirements for the [PRODUCT_NAME] in the NOTICE file?
> --------------------------------------------------------------------
>                 Key: LEGAL-84
>                 URL: https://issues.apache.org/jira/browse/LEGAL-84
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: ant elder
> The NOTICE file in released artifacts must start with Apache [PRODUCT_NAME], as described
at http://apache.org/legal/src-headers.html#notice
> Many many projects extend the product name with text describing the particular artifcat,
eg "Apache HttpComponents Client", often .jar artifacts created by Maven use the Maven module
artifact name in the NOTICE file and frequently thats done using maven keyword expansion with
"${project.name}". Its also quite common for this customized name to go wrong and the resulting
NOTICE file either having the wrong name as it was copied from some other artifacts NOTICE
or else just include Apache ${project.name} as the key word expansion has failed.
> It seems like it would be much simpler and less likely to go wrong if the name didn't
need to be customized for individual artifacts, so my questions is: are there any legal or
policy reasons or requirement to include anything additional over just the projects TLP name?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message