Return-Path: X-Original-To: apmail-maven-dev-archive@www.apache.org Delivered-To: apmail-maven-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD434CE3F for ; Sun, 21 Jul 2013 13:06:12 +0000 (UTC) Received: (qmail 15869 invoked by uid 500); 21 Jul 2013 13:06:10 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 15781 invoked by uid 500); 21 Jul 2013 13:06:09 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 15771 invoked by uid 99); 21 Jul 2013 13:06:07 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Jul 2013 13:06:07 +0000 Received: from localhost (HELO mail-wg0-f47.google.com) (127.0.0.1) (smtp-auth username olamy, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Jul 2013 13:06:06 +0000 Received: by mail-wg0-f47.google.com with SMTP id j13so252397wgh.26 for ; Sun, 21 Jul 2013 06:06:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=PieU5qb+s8z74/ymZfRxlf+lwzYi+ZNg/lupLx5ybQg=; b=O1XgPYIQv/eIgddbCteEtv73Sdy35kewDDxS5F5Ml+NdAu6wQh0t8CVKh80qK1UJxH 5kv/aQYJ9ZKDy7q2GwTd46sTnc6/3sVip+NQVP7meIBxhF0Q0G5AeR+doZN/CyQ0Fadl tvdHVk+lQMkXbjFmcG2C2ajzM0tzoXrybNX9gMvp9nR7bPMXheyjtEWczyNVT3FALZY3 Znr87hXiwsRH/8ALM/RdF57ea5g+XcLxY2BOpLglbfU7BE3es3tya8crVuq+yLOiQh2M 2SDnbuaTNIvBTFbkzVa0TcpxVPAPFvcUWxl8Yjsx968sczVtSklzbXctgKJfOKNj7olj fG6A== X-Received: by 10.180.184.12 with SMTP id eq12mr6521135wic.8.1374411964900; Sun, 21 Jul 2013 06:06:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.87.135 with HTTP; Sun, 21 Jul 2013 06:05:44 -0700 (PDT) In-Reply-To: References: <20130720125834.F14BD23888E2@eris.apache.org> From: Olivier Lamy Date: Sun, 21 Jul 2013 23:05:44 +1000 Message-ID: Subject: Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE To: Maven Developers List Content-Type: text/plain; charset=ISO-8859-1 2013/7/21 sebb : > On 21 July 2013 13:30, Robert Scholte wrote: >> "Also, the files change relatively rarely once set up." >> >> I thought you strongly believed in Murphy's Law... > > Not sure how that is relevant. > >> >> I agree with Dennis: let's ask for the *facts* why these files are required >> here. > > Robert already quoted this earlier in the thread: > From http://www.apache.org/dev/licensing-howto.html#source-tree-location > > If you think that's wrong, it needs to be take up with Infra. why infra? they decide about our licensing mode? > >> If it is because they need to be included in the source-release file, >> then add them additionally instead of maintaining them per project. > > No, they need to be included in SCM as well. > > Since the SCM tree is basically what becomes the source archive, the > same files will do for both. > It's trivial to include the files in the source assembly descriptor so > they become part of the source archive. > >> >> Op Sun, 21 Jul 2013 14:17:12 +0200 schreef sebb : >> >>> On 21 July 2013 13:09, Dennis Lundberg 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. >>> >>> >>> And some things are not readily automateable - AFAIK there is no >>> accuratate data from which to automate this. >>> How do you track code imports with copyright statements? There are >>> several different ways to treat these. >>> Also, different licenses have different attribution requirements, and >>> for ones that do require attribution it has to be determined from the >>> license, which does not have a fixed format. >>> >>> Also, the files change relatively rarely once set up. >>> Addition of 3rd party source or binaries to the archives is the main >>> reason to change the N&L files. >>> >>>> 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" : >>>> >>>>> From 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 >>>>> >>>> >: >>>>> >>>>> 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 : >>>>>> >>>>>>> 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 >>>>>>> ==============================**==============================** >>>>>>> ================== >>>>>>> --- 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/ >>>>>>> + >>>>>>> + 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 >>>>>>> + >>>>>>> + 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 >>>>>>> ==============================**==============================** >>>>>>> ================== >>>>>>> --- 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 >>>>> For additional commands, e-mail: dev-help@maven.apache.org >>>>> >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org >>> >>> For additional commands, e-mail: dev-help@maven.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org >> >> For additional commands, e-mail: dev-help@maven.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org > For additional commands, e-mail: dev-help@maven.apache.org > -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org