On 21 July 2013 13:38, Daniel Kulp <dk...@apache.org> wrote: > > Also keep in mind, there is likely a large difference between the > LICENSE/NOTICE files that would go into a "source release" than would go into > the binary convenience releases. 90% of the source NOTICE/LICESE files are > just plain Apache License and the simple 4 line NOTICE.
Agreed. <pedantMode>there are 4 non-blank lines; there is another blank line in the middle</pedantMode> > For the binary, the LICENSE needs links to the license of all the other jars > shipped in the package. It also MAY need extra notices in the NOTICE. The > RR plugin certainly can help with the first part of that. But remember that only bits that are actually included in the binary archive should be mentioned in N&L. Unless a dependency is actually bundled in the archive, it does not count as far as the N&L are concerned. > Dan > > > On Jul 21, 2013, at 8:09 AM, Dennis Lundberg <denn...@apache.org> wrote: > >> Hi >> >> Has anyone asked if we can use generated files instead? >> >> Many of the ASF rules are written by people that have not concidered the >> fact that things such as these can be automated. Therefore many of these >> rules are stated in a way that does not fit directly into the Maven way of >> doing things. >> >> We do include these files in "every Apache distribution" we make. It's just >> that we do not store them in SCM. >> >> -- >> Dennis Lundberg >> Den 21 jul 2013 11:13 skrev "Robert Scholte" <rfscho...@apache.org>: >> >>> From http://www.apache.org/dev/**licensing-howto.html#source-** >>> tree-location<http://www.apache.org/dev/licensing-howto.html#source-tree-location> >>> >>> "Location Within the Source Tree >>> >>> LICENSE and NOTICE belong at the top level of the source tree. They may be >>> named LICENSE.txt and NOTICE.txt, but the bare names are preferred." >>> >>> If you consider a release root as the top level of the source tree, then >>> they need to be placed here. >>> And yes, I'm aware that they are already bundled with the binairy, but >>> these lines are quite clear where these files are expected. >>> >>> Robert >>> >>> Op Sun, 21 Jul 2013 08:57:28 +0200 schreef Olivier Lamy <ol...@apache.org >>>> : >>> >>> why? >>>> Is it mandatory? If yes I'd like to have some links. >>>> AFAIK those files are generated. >>>> This mean we will have to add those files for all artifacts we produce. >>>> If one day the content change we will have to change all files in the >>>> scm instead of only the plugin which generate that. >>>> >>>> Seriously? >>>> >>>> 2013/7/20 <rfscho...@apache.org>: >>>> >>>>> Author: rfscholte >>>>> Date: Sat Jul 20 12:58:34 2013 >>>>> New Revision: 1505129 >>>>> >>>>> URL: http://svn.apache.org/r1505129 >>>>> Log: >>>>> Add LICENSE and NOTICE files >>>>> >>>>> Added: >>>>> maven/plugins/trunk/maven-**install-plugin/LICENSE >>>>> maven/plugins/trunk/maven-**install-plugin/NOTICE >>>>> >>>>> Added: maven/plugins/trunk/maven-**install-plugin/LICENSE >>>>> URL: http://svn.apache.org/viewvc/**maven/plugins/trunk/maven-** >>>>> install-plugin/LICENSE?rev=**1505129&view=auto<http://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129&view=auto> >>>>> ==============================**==============================** >>>>> ================== >>>>> --- maven/plugins/trunk/maven-**install-plugin/LICENSE (added) >>>>> +++ maven/plugins/trunk/maven-**install-plugin/LICENSE Sat Jul 20 >>>>> 12:58:34 2013 >>>>> @@ -0,0 +1,202 @@ >>>>> + >>>>> + Apache License >>>>> + Version 2.0, January 2004 >>>>> + >>>>> http://www.apache.org/**licenses/<http://www.apache.org/licenses/> >>>>> + >>>>> + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION >>>>> + >>>>> + 1. Definitions. >>>>> + >>>>> + "License" shall mean the terms and conditions for use, >>>>> reproduction, >>>>> + and distribution as defined by Sections 1 through 9 of this >>>>> document. >>>>> + >>>>> + "Licensor" shall mean the copyright owner or entity authorized by >>>>> + the copyright owner that is granting the License. >>>>> + >>>>> + "Legal Entity" shall mean the union of the acting entity and all >>>>> + other entities that control, are controlled by, or are under >>>>> common >>>>> + control with that entity. For the purposes of this definition, >>>>> + "control" means (i) the power, direct or indirect, to cause the >>>>> + direction or management of such entity, whether by contract or >>>>> + otherwise, or (ii) ownership of fifty percent (50%) or more of the >>>>> + outstanding shares, or (iii) beneficial ownership of such entity. >>>>> + >>>>> + "You" (or "Your") shall mean an individual or Legal Entity >>>>> + exercising permissions granted by this License. >>>>> + >>>>> + "Source" form shall mean the preferred form for making >>>>> modifications, >>>>> + including but not limited to software source code, documentation >>>>> + source, and configuration files. >>>>> + >>>>> + "Object" form shall mean any form resulting from mechanical >>>>> + transformation or translation of a Source form, including but >>>>> + not limited to compiled object code, generated documentation, >>>>> + and conversions to other media types. >>>>> + >>>>> + "Work" shall mean the work of authorship, whether in Source or >>>>> + Object form, made available under the License, as indicated by a >>>>> + copyright notice that is included in or attached to the work >>>>> + (an example is provided in the Appendix below). >>>>> + >>>>> + "Derivative Works" shall mean any work, whether in Source or >>>>> Object >>>>> + form, that is based on (or derived from) the Work and for which >>>>> the >>>>> + editorial revisions, annotations, elaborations, or other >>>>> modifications >>>>> + represent, as a whole, an original work of authorship. For the >>>>> purposes >>>>> + of this License, Derivative Works shall not include works that >>>>> remain >>>>> + separable from, or merely link (or bind by name) to the >>>>> interfaces of, >>>>> + the Work and Derivative Works thereof. >>>>> + >>>>> + "Contribution" shall mean any work of authorship, including >>>>> + the original version of the Work and any modifications or >>>>> additions >>>>> + to that Work or Derivative Works thereof, that is intentionally >>>>> + submitted to Licensor for inclusion in the Work by the copyright >>>>> owner >>>>> + or by an individual or Legal Entity authorized to submit on >>>>> behalf of >>>>> + the copyright owner. For the purposes of this definition, >>>>> "submitted" >>>>> + means any form of electronic, verbal, or written communication >>>>> sent >>>>> + to the Licensor or its representatives, including but not limited >>>>> to >>>>> + communication on electronic mailing lists, source code control >>>>> systems, >>>>> + and issue tracking systems that are managed by, or on behalf of, >>>>> the >>>>> + Licensor for the purpose of discussing and improving the Work, but >>>>> + excluding communication that is conspicuously marked or otherwise >>>>> + designated in writing by the copyright owner as "Not a >>>>> Contribution." >>>>> + >>>>> + "Contributor" shall mean Licensor and any individual or Legal >>>>> Entity >>>>> + on behalf of whom a Contribution has been received by Licensor and >>>>> + subsequently incorporated within the Work. >>>>> + >>>>> + 2. Grant of Copyright License. Subject to the terms and conditions of >>>>> + this License, each Contributor hereby grants to You a perpetual, >>>>> + worldwide, non-exclusive, no-charge, royalty-free, irrevocable >>>>> + copyright license to reproduce, prepare Derivative Works of, >>>>> + publicly display, publicly perform, sublicense, and distribute the >>>>> + Work and such Derivative Works in Source or Object form. >>>>> + >>>>> + 3. Grant of Patent License. Subject to the terms and conditions of >>>>> + this License, each Contributor hereby grants to You a perpetual, >>>>> + worldwide, non-exclusive, no-charge, royalty-free, irrevocable >>>>> + (except as stated in this section) patent license to make, have >>>>> made, >>>>> + use, offer to sell, sell, import, and otherwise transfer the Work, >>>>> + where such license applies only to those patent claims licensable >>>>> + by such Contributor that are necessarily infringed by their >>>>> + Contribution(s) alone or by combination of their Contribution(s) >>>>> + with the Work to which such Contribution(s) was submitted. If You >>>>> + institute patent litigation against any entity (including a >>>>> + cross-claim or counterclaim in a lawsuit) alleging that the Work >>>>> + or a Contribution incorporated within the Work constitutes direct >>>>> + or contributory patent infringement, then any patent licenses >>>>> + granted to You under this License for that Work shall terminate >>>>> + as of the date such litigation is filed. >>>>> + >>>>> + 4. Redistribution. You may reproduce and distribute copies of the >>>>> + Work or Derivative Works thereof in any medium, with or without >>>>> + modifications, and in Source or Object form, provided that You >>>>> + meet the following conditions: >>>>> + >>>>> + (a) You must give any other recipients of the Work or >>>>> + Derivative Works a copy of this License; and >>>>> + >>>>> + (b) You must cause any modified files to carry prominent notices >>>>> + stating that You changed the files; and >>>>> + >>>>> + (c) You must retain, in the Source form of any Derivative Works >>>>> + that You distribute, all copyright, patent, trademark, and >>>>> + attribution notices from the Source form of the Work, >>>>> + excluding those notices that do not pertain to any part of >>>>> + the Derivative Works; and >>>>> + >>>>> + (d) If the Work includes a "NOTICE" text file as part of its >>>>> + distribution, then any Derivative Works that You distribute >>>>> must >>>>> + include a readable copy of the attribution notices contained >>>>> + within such NOTICE file, excluding those notices that do not >>>>> + pertain to any part of the Derivative Works, in at least one >>>>> + of the following places: within a NOTICE text file distributed >>>>> + as part of the Derivative Works; within the Source form or >>>>> + documentation, if provided along with the Derivative Works; >>>>> or, >>>>> + within a display generated by the Derivative Works, if and >>>>> + wherever such third-party notices normally appear. The >>>>> contents >>>>> + of the NOTICE file are for informational purposes only and >>>>> + do not modify the License. You may add Your own attribution >>>>> + notices within Derivative Works that You distribute, alongside >>>>> + or as an addendum to the NOTICE text from the Work, provided >>>>> + that such additional attribution notices cannot be construed >>>>> + as modifying the License. >>>>> + >>>>> + You may add Your own copyright statement to Your modifications and >>>>> + may provide additional or different license terms and conditions >>>>> + for use, reproduction, or distribution of Your modifications, or >>>>> + for any such Derivative Works as a whole, provided Your use, >>>>> + reproduction, and distribution of the Work otherwise complies with >>>>> + the conditions stated in this License. >>>>> + >>>>> + 5. Submission of Contributions. Unless You explicitly state >>>>> otherwise, >>>>> + any Contribution intentionally submitted for inclusion in the Work >>>>> + by You to the Licensor shall be under the terms and conditions of >>>>> + this License, without any additional terms or conditions. >>>>> + Notwithstanding the above, nothing herein shall supersede or >>>>> modify >>>>> + the terms of any separate license agreement you may have executed >>>>> + with Licensor regarding such Contributions. >>>>> + >>>>> + 6. Trademarks. This License does not grant permission to use the >>>>> trade >>>>> + names, trademarks, service marks, or product names of the >>>>> Licensor, >>>>> + except as required for reasonable and customary use in describing >>>>> the >>>>> + origin of the Work and reproducing the content of the NOTICE file. >>>>> + >>>>> + 7. Disclaimer of Warranty. Unless required by applicable law or >>>>> + agreed to in writing, Licensor provides the Work (and each >>>>> + Contributor provides its Contributions) on an "AS IS" BASIS, >>>>> + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or >>>>> + implied, including, without limitation, any warranties or >>>>> conditions >>>>> + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A >>>>> + PARTICULAR PURPOSE. You are solely responsible for determining the >>>>> + appropriateness of using or redistributing the Work and assume any >>>>> + risks associated with Your exercise of permissions under this >>>>> License. >>>>> + >>>>> + 8. Limitation of Liability. In no event and under no legal theory, >>>>> + whether in tort (including negligence), contract, or otherwise, >>>>> + unless required by applicable law (such as deliberate and grossly >>>>> + negligent acts) or agreed to in writing, shall any Contributor be >>>>> + liable to You for damages, including any direct, indirect, >>>>> special, >>>>> + incidental, or consequential damages of any character arising as a >>>>> + result of this License or out of the use or inability to use the >>>>> + Work (including but not limited to damages for loss of goodwill, >>>>> + work stoppage, computer failure or malfunction, or any and all >>>>> + other commercial damages or losses), even if such Contributor >>>>> + has been advised of the possibility of such damages. >>>>> + >>>>> + 9. Accepting Warranty or Additional Liability. While redistributing >>>>> + the Work or Derivative Works thereof, You may choose to offer, >>>>> + and charge a fee for, acceptance of support, warranty, indemnity, >>>>> + or other liability obligations and/or rights consistent with this >>>>> + License. However, in accepting such obligations, You may act only >>>>> + on Your own behalf and on Your sole responsibility, not on behalf >>>>> + of any other Contributor, and only if You agree to indemnify, >>>>> + defend, and hold each Contributor harmless for any liability >>>>> + incurred by, or claims asserted against, such Contributor by >>>>> reason >>>>> + of your accepting any such warranty or additional liability. >>>>> + >>>>> + END OF TERMS AND CONDITIONS >>>>> + >>>>> + APPENDIX: How to apply the Apache License to your work. >>>>> + >>>>> + To apply the Apache License to your work, attach the following >>>>> + boilerplate notice, with the fields enclosed by brackets "[]" >>>>> + replaced with your own identifying information. (Don't include >>>>> + the brackets!) The text should be enclosed in the appropriate >>>>> + comment syntax for the file format. We also recommend that a >>>>> + file or class name and description of purpose be included on the >>>>> + same "printed page" as the copyright notice for easier >>>>> + identification within third-party archives. >>>>> + >>>>> + Copyright [yyyy] [name of copyright owner] >>>>> + >>>>> + Licensed under the Apache License, Version 2.0 (the "License"); >>>>> + you may not use this file except in compliance with the License. >>>>> + You may obtain a copy of the License at >>>>> + >>>>> + >>>>> http://www.apache.org/**licenses/LICENSE-2.0<http://www.apache.org/licenses/LICENSE-2.0> >>>>> + >>>>> + Unless required by applicable law or agreed to in writing, software >>>>> + distributed under the License is distributed on an "AS IS" BASIS, >>>>> + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or >>>>> implied. >>>>> + See the License for the specific language governing permissions and >>>>> + limitations under the License. >>>>> >>>>> Added: maven/plugins/trunk/maven-**install-plugin/NOTICE >>>>> URL: http://svn.apache.org/viewvc/**maven/plugins/trunk/maven-** >>>>> install-plugin/NOTICE?rev=**1505129&view=auto<http://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/NOTICE?rev=1505129&view=auto> >>>>> ==============================**==============================** >>>>> ================== >>>>> --- maven/plugins/trunk/maven-**install-plugin/NOTICE (added) >>>>> +++ maven/plugins/trunk/maven-**install-plugin/NOTICE Sat Jul 20 >>>>> 12:58:34 2013 >>>>> @@ -0,0 +1,5 @@ >>>>> +Apache Maven Install Plugin >>>>> +Copyright 2007-2013 The Apache Software Foundation >>>>> + >>>>> +This product includes software developed at >>>>> +The Apache Software Foundation (http://www.apache.org/). >>>>> >>>>> >>>>> >>>> >>>> >>> ------------------------------**------------------------------**--------- >>> To unsubscribe, e-mail: >>> dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
