Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
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=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
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 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=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
Damned there are plenty of Apache projects which don't do that :-) But in this case the plugin maven-remote-resources-plugin doesn't have to be used anymore? Because now we can have duplicate NL with possible different content. As one will be maintained manually which mean we can miss to add content etc... But so 2013/7/21 Robert Scholte rfscho...@apache.org: 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 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=1505129view=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 +
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
On 21 July 2013 11:48, Olivier Lamy ol...@apache.org wrote: Damned there are plenty of Apache projects which don't do that :-) They will have to be fixed over time. But in this case the plugin maven-remote-resources-plugin doesn't have to be used anymore? Because now we can have duplicate NL with possible different content. As one will be maintained manually which mean we can miss to add content etc... AIUI remote resources does not automagically update the NL files; it also has to be manually configured by using appended resources. About the only thing RR does do is insert the year and project name details. And only the year might need changing once the correct NL files have been set up initially. [And I have seen projects where the autoconfig of project name causes problems - e.g. if the project uses a separate module to build the dist archives] AFAICT both approaches require manual configuration of the same information - it's just held in different places. But so 2013/7/21 Robert Scholte rfscho...@apache.org: 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 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=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
Having a copy here does indeed mean we have to maintain it, unless we use svn:externals (but better not do that). If I'm correct, both files contain custom 'fields', referring to the name of the project and/or a year or date. Also, I'm always having trouble with year ranges: suppose the range is 2005-2013, what does this mean in 2014? Anyhow, sounds like another enforcer-rule is required, maybe a specific ASF-ruleset Robert Op Sun, 21 Jul 2013 13:03:18 +0200 schreef sebb seb...@gmail.com: On 21 July 2013 11:48, Olivier Lamy ol...@apache.org wrote: Damned there are plenty of Apache projects which don't do that :-) They will have to be fixed over time. But in this case the plugin maven-remote-resources-plugin doesn't have to be used anymore? Because now we can have duplicate NL with possible different content. As one will be maintained manually which mean we can miss to add content etc... AIUI remote resources does not automagically update the NL files; it also has to be manually configured by using appended resources. About the only thing RR does do is insert the year and project name details. And only the year might need changing once the correct NL files have been set up initially. [And I have seen projects where the autoconfig of project name causes problems - e.g. if the project uses a separate module to build the dist archives] AFAICT both approaches require manual configuration of the same information - it's just held in different places. But so 2013/7/21 Robert Scholte rfscho...@apache.org: 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 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=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
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-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
On 21 July 2013 12:39, Robert Scholte rfscho...@apache.org wrote: Having a copy here does indeed mean we have to maintain it, unless we use svn:externals (but better not do that). If I'm correct, both files contain custom 'fields', referring to the name of the project and/or a year or date. both files - which files are those? Also, I'm always having trouble with year ranges: suppose the range is 2005-2013, what does this mean in 2014? The way the range has often been interpreted is inceptionYear-currentYear. I think the idea is that the copyright year is changed whenever there is a substantial change to the collective work (i.e. to which the Copyright applies) That normally means the latest year is updated to the year of the release. But given that copyright lasts a long time, it may not matter if it is not always updated. Anyhow, sounds like another enforcer-rule is required, maybe a specific ASF-ruleset Robert Op Sun, 21 Jul 2013 13:03:18 +0200 schreef sebb seb...@gmail.com: On 21 July 2013 11:48, Olivier Lamy ol...@apache.org wrote: Damned there are plenty of Apache projects which don't do that :-) They will have to be fixed over time. But in this case the plugin maven-remote-resources-plugin doesn't have to be used anymore? Because now we can have duplicate NL with possible different content. As one will be maintained manually which mean we can miss to add content etc... AIUI remote resources does not automagically update the NL files; it also has to be manually configured by using appended resources. About the only thing RR does do is insert the year and project name details. And only the year might need changing once the correct NL files have been set up initially. [And I have seen projects where the autoconfig of project name causes problems - e.g. if the project uses a separate module to build the dist archives] AFAICT both approaches require manual configuration of the same information - it's just held in different places. But so 2013/7/21 Robert Scholte rfscho...@apache.org: 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 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=1505129view=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,
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
On 21 July 2013 13:09, 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. 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 NL 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 rfscho...@apache.org: From http://www.apache.org/dev/**licensing-howto.html#source-** tree-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
Op Sun, 21 Jul 2013 14:10:12 +0200 schreef sebb seb...@gmail.com: On 21 July 2013 12:39, Robert Scholte rfscho...@apache.org wrote: Having a copy here does indeed mean we have to maintain it, unless we use svn:externals (but better not do that). If I'm correct, both files contain custom 'fields', referring to the name of the project and/or a year or date. both files - which files are those? LICENSE and NOTICE Also, I'm always having trouble with year ranges: suppose the range is 2005-2013, what does this mean in 2014? The way the range has often been interpreted is inceptionYear-currentYear. I think the idea is that the copyright year is changed whenever there is a substantial change to the collective work (i.e. to which the Copyright applies) That normally means the latest year is updated to the year of the release. But given that copyright lasts a long time, it may not matter if it is not always updated. If currentYear has no meaningful value for the copyright, why not drop it? Now it reads like the copyright only covers the range, that's not true. Anyhow, sounds like another enforcer-rule is required, maybe a specific ASF-ruleset Robert Op Sun, 21 Jul 2013 13:03:18 +0200 schreef sebb seb...@gmail.com: On 21 July 2013 11:48, Olivier Lamy ol...@apache.org wrote: Damned there are plenty of Apache projects which don't do that :-) They will have to be fixed over time. But in this case the plugin maven-remote-resources-plugin doesn't have to be used anymore? Because now we can have duplicate NL with possible different content. As one will be maintained manually which mean we can miss to add content etc... AIUI remote resources does not automagically update the NL files; it also has to be manually configured by using appended resources. About the only thing RR does do is insert the year and project name details. And only the year might need changing once the correct NL files have been set up initially. [And I have seen projects where the autoconfig of project name causes problems - e.g. if the project uses a separate module to build the dist archives] AFAICT both approaches require manual configuration of the same information - it's just held in different places. But so 2013/7/21 Robert Scholte rfscho...@apache.org: 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 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=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
Also, the files change relatively rarely once set up. I thought you strongly believed in Murphy's Law... I agree with Dennis: let's ask for the *facts* why these files are required here. If it is because they need to be included in the source-release file, then add them additionally instead of maintaining them per project. Op Sun, 21 Jul 2013 14:17:12 +0200 schreef sebb seb...@gmail.com: On 21 July 2013 13:09, 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. 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 NL 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 rfscho...@apache.org: From http://www.apache.org/dev/**licensing-howto.html#source-** tree-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
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. 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. 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-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
On 21 July 2013 13:22, Robert Scholte rfscho...@apache.org wrote: Op Sun, 21 Jul 2013 14:10:12 +0200 schreef sebb seb...@gmail.com: On 21 July 2013 12:39, Robert Scholte rfscho...@apache.org wrote: Having a copy here does indeed mean we have to maintain it, unless we use svn:externals (but better not do that). If I'm correct, both files contain custom 'fields', referring to the name of the project and/or a year or date. both files - which files are those? LICENSE and NOTICE The LICENSE file is fixed - it should contain the text of AL 2.0, which does not have configurable dates/project names. Don't be misled by the bit at the bottom after the license proper - that is a template for 3rd parties to use; it should not be pre-configured by the ASF project. It could (should?) probably be omitted. Also, I'm always having trouble with year ranges: suppose the range is 2005-2013, what does this mean in 2014? The way the range has often been interpreted is inceptionYear-currentYear. I think the idea is that the copyright year is changed whenever there is a substantial change to the collective work (i.e. to which the Copyright applies) That normally means the latest year is updated to the year of the release. But given that copyright lasts a long time, it may not matter if it is not always updated. If currentYear has no meaningful value for the copyright, why not drop it? I did not say it had no meaning, only that it does not have to be 100% up to date. Now it reads like the copyright only covers the range, that's not true. Not sure what you mean by that. Anyhow, sounds like another enforcer-rule is required, maybe a specific ASF-ruleset Robert Op Sun, 21 Jul 2013 13:03:18 +0200 schreef sebb seb...@gmail.com: On 21 July 2013 11:48, Olivier Lamy ol...@apache.org wrote: Damned there are plenty of Apache projects which don't do that :-) They will have to be fixed over time. But in this case the plugin maven-remote-resources-plugin doesn't have to be used anymore? Because now we can have duplicate NL with possible different content. As one will be maintained manually which mean we can miss to add content etc... AIUI remote resources does not automagically update the NL files; it also has to be manually configured by using appended resources. About the only thing RR does do is insert the year and project name details. And only the year might need changing once the correct NL files have been set up initially. [And I have seen projects where the autoconfig of project name causes problems - e.g. if the project uses a separate module to build the dist archives] AFAICT both approaches require manual configuration of the same information - it's just held in different places. But so 2013/7/21 Robert Scholte rfscho...@apache.org: 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 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=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
On 21 July 2013 13:30, Robert Scholte rfscho...@apache.org 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. 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 seb...@gmail.com: On 21 July 2013 13:09, 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. 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 NL 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 rfscho...@apache.org: From http://www.apache.org/dev/**licensing-howto.html#source-** tree-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
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. pedantModethere 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 NL. Unless a dependency is actually bundled in the archive, it does not count as far as the NL 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-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
2013/7/21 sebb seb...@gmail.com: On 21 July 2013 13:30, Robert Scholte rfscho...@apache.org 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 seb...@gmail.com: On 21 July 2013 13:09, 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. 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 NL 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 rfscho...@apache.org: From http://www.apache.org/dev/**licensing-howto.html#source-** tree-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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,
Re: svn commit: r1505129 - in /maven/plugins/trunk/maven-install-plugin: LICENSE NOTICE
On 21 July 2013 14:05, Olivier Lamy ol...@apache.org wrote: 2013/7/21 sebb seb...@gmail.com: On 21 July 2013 13:30, Robert Scholte rfscho...@apache.org 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? They are responsible for the dev/ pages. 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 seb...@gmail.com: On 21 July 2013 13:09, 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. 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 NL 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 rfscho...@apache.org: From http://www.apache.org/dev/**licensing-howto.html#source-** tree-locationhttp://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=**1505129view=autohttp://svn.apache.org/viewvc/maven/plugins/trunk/maven-install-plugin/LICENSE?rev=1505129view=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
