Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna
Hi, I got the same error when I tried to use the p2 site in my Buckminster build for Graphiti and was not able to get it working. In the end I also used the Git repo directly; it seems this is the only way to make it work. Michael From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Ed Willink Sent: Donnerstag, 24. April 2014 20:34 To: Cross project issues Subject: Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna Hi Is anyone able to make http://download.eclipse.org/cbi/updates/license work with Buckmnister? I get CSpec org.eclipse.license:eclipse.feature$1.0.1.v20140414-1359 has no action, group, or local artifact named jar.contents Hence my recommendation on https://bugs.eclipse.org/bugs/show_bug.cgi?id=431255 to use the GIT rather than P2 repo. Regards Ed Willink On 24/04/2014 18:24, David M Williams wrote: Just to confirm, what Andreas said is accurate, the best place to get the shared license from is the cbi license repo, http://download.eclipse.org/cbi/updates/license But, also wanted to add, some projects have their own copy of the license in their own repo, and then feature in their project share that license. That's still fine, if people would prefer that. And, I've heard, some projects still use the old method of non-shared license. That's fine too, from Sim Rel point of view ... it is a lot more copy/paste, but just wanted to be clear it is not required to use the cbi repo ... it's just required to use a common license. I hope most find the CBI provided shared version an easy way to implement common license -- its certainly easier in the long run ... but, admittedly is you are not doing it right now, it's probably about the same amount of work to convert vs. doing a bunch of copy/paste operations. HTH (if not, please ask again). From:Igor Fedorenko i...@ifedorenko.commailto:i...@ifedorenko.com To: cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org Date:04/24/2014 06:54 AM Subject:Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna Sent by: cross-project-issues-dev-boun...@eclipse.orgmailto:cross-project-issues-dev-boun...@eclipse.org David, With 60+ comments on the bug you linked, it's hard to understand what individual projects are expected to do. What license feature are we supposed to use now? Is it available from Luna symrel composite repo already? -- Regards, Igor On 2014-04-24, 4:41, David M Williams wrote: I'm sure everyone is aware of the new license requirement: *_Bug 431255_* https://bugs.eclipse.org/bugs/show_bug.cgi?id=431255- Need to update the SUA (Software User Agreement) And now that we in Platform (and MPC) have updated -- which demonstrated my updated repo report appears to be working correctly -- I thought it'd be a good time to send a reminder. http://build.eclipse.org/simrel/luna/reporeports/reports/licenseConsistency.html It'd be nice to get as many updated as possible for M7, and certainly by RC1. It really does give a much better user experience and better first impression to those updating/installing to get that simpler, more meaningful license dialog. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2014.0.4569 / Virus Database: 3920/7389 - Release Date: 04/24/14 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna
Hi, Sorry in advance if this is covered ground somewhere...but I can't seem to find it. For those projects that are still using the 'old way'...and therefore need to update the files by hand...I want to clarify what actually needs to be updated to meet these requirements...please correct if wrong/missing, etc: In the features: notice.html (the SUA in it's own content) feature.properties (the SUA in the feature.properties file) That's it, right? I've got the new content from the legal git repo, but want to verify that this is the extent of the necessary changes. Has anyone created and shared among EF projects a script to do this? Not that I'll actually use it :), but useful to ask. Thanks, Scott On 4/24/2014 1:41 AM, David M Williams wrote: I'm sure everyone is aware of the new license requirement: *_Bug 431255_* https://bugs.eclipse.org/bugs/show_bug.cgi?id=431255- Need to update the SUA (Software User Agreement) And now that we in Platform (and MPC) have updated -- which demonstrated my updated repo report appears to be working correctly -- I thought it'd be a good time to send a reminder. http://build.eclipse.org/simrel/luna/reporeports/reports/licenseConsistency.html It'd be nice to get as many updated as possible for M7, and certainly by RC1. It really does give a much better user experience and better first impression to those updating/installing to get that simpler, more meaningful license dialog. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna
That sound about right, Scott. If you ever need to check in extreme detail, the authoritative guide is http://www.eclipse.org/legal/guidetolegaldoc.php According to it, even though document and content is the same, notice.html is what should be at the root of zip files. and in the features themselves, it is called license.html (even though it is not really a license). So beside having have the two files in root of each feature (license.html and epl-v10.html [unchanged, frm previous]) the feature.properties has two properties, licenseURL=license.html [which likely doesn't have to change, if name of file stays the same], and then license=plain text of license.html When adding the plain text version to properties, be sure to maintain the tabs and end of lines (Linux form) as they are ... which if you pull from git, should be easy, if you get from website, such as from http://www.eclipse.org/legal/epl/feature.properties.txt when be sure to use something like wget http://www.eclipse.org/legal/epl/feature.properties.txt Using the browsers save as function may change characters in ways you wouldn't want them changed!. HTH From: Scott Lewis sle...@composent.com To: cross-project-issues-dev@eclipse.org, Date: 04/25/2014 12:26 PM Subject:Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna Sent by:cross-project-issues-dev-boun...@eclipse.org Hi, Sorry in advance if this is covered ground somewhere...but I can't seem to find it. For those projects that are still using the 'old way'...and therefore need to update the files by hand...I want to clarify what actually needs to be updated to meet these requirements...please correct if wrong/missing, etc: In the features: notice.html (the SUA in it's own content) feature.properties (the SUA in the feature.properties file) That's it, right? I've got the new content from the legal git repo, but want to verify that this is the extent of the necessary changes. Has anyone created and shared among EF projects a script to do this? Not that I'll actually use it :), but useful to ask. Thanks, Scott On 4/24/2014 1:41 AM, David M Williams wrote: I'm sure everyone is aware of the new license requirement: Bug 431255 - Need to update the SUA (Software User Agreement) And now that we in Platform (and MPC) have updated -- which demonstrated my updated repo report appears to be working correctly -- I thought it'd be a good time to send a reminder. http://build.eclipse.org/simrel/luna/reporeports/reports/licenseConsistency.html It'd be nice to get as many updated as possible for M7, and certainly by RC1. It really does give a much better user experience and better first impression to those updating/installing to get that simpler, more meaningful license dialog. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna
On 25/04/2014 2:54 PM, David M Williams wrote: If you ever need to check in extreme detail, the authoritative guide is http://www.eclipse.org/legal/guidetolegaldoc.php On that topic: If anyone reading that document (or anything else on the legal page[1]) notices any errors or omissions, please feel free to open a bug and assign it to me. Thanks. [1] http://www.eclipse.org/legal/ -- Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 (mobile) EclipseCon France 2014 http://www.eclipsecon.org/france2014 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna
Hi Igor, With 60+ comments on the bug you linked, it's hard to understand what individual projects are expected to do. What license feature are we supposed to use now? Is it available from Luna symrel composite repo already? Here's what served us well at Code Recommenders. In our target file, we use CBI license repository rather then the simrel repo: location includeAllPlatforms=false includeConfigurePhase=false includeMode=slicer includeSource=true type=InstallableUnit unit id=org.eclipse.license.feature.group version=0.0.0/ repository location=http://download.eclipse.org/cbi/updates/license/ /location In our feature.xml: feature ... license-feature=org.eclipse.license license-feature-version=0.0.0 license url=%licenseURL %license /license This picked up the change in license automatically upon the next (Tycho-based) build. Hope that helps. Andreas -- Codetrails UG (haftungsbeschränkt) The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Mobile: +49-170-811-3791 http://www.codetrails.com/ Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna
Just to confirm, what Andreas said is accurate, the best place to get the shared license from is the cbi license repo, http://download.eclipse.org/cbi/updates/license But, also wanted to add, some projects have their own copy of the license in their own repo, and then feature in their project share that license. That's still fine, if people would prefer that. And, I've heard, some projects still use the old method of non-shared license. That's fine too, from Sim Rel point of view ... it is a lot more copy/paste, but just wanted to be clear it is not required to use the cbi repo ... it's just required to use a common license. I hope most find the CBI provided shared version an easy way to implement common license -- its certainly easier in the long run ... but, admittedly is you are not doing it right now, it's probably about the same amount of work to convert vs. doing a bunch of copy/paste operations. HTH (if not, please ask again). From: Igor Fedorenko i...@ifedorenko.com To: cross-project-issues-dev@eclipse.org Date: 04/24/2014 06:54 AM Subject:Re: [cross-project-issues-dev] Reminder to update your feature licenses for Luna Sent by:cross-project-issues-dev-boun...@eclipse.org David, With 60+ comments on the bug you linked, it's hard to understand what individual projects are expected to do. What license feature are we supposed to use now? Is it available from Luna symrel composite repo already? -- Regards, Igor On 2014-04-24, 4:41, David M Williams wrote: I'm sure everyone is aware of the new license requirement: *_Bug 431255_* https://bugs.eclipse.org/bugs/show_bug.cgi?id=431255- Need to update the SUA (Software User Agreement) And now that we in Platform (and MPC) have updated -- which demonstrated my updated repo report appears to be working correctly -- I thought it'd be a good time to send a reminder. http://build.eclipse.org/simrel/luna/reporeports/reports/licenseConsistency.html It'd be nice to get as many updated as possible for M7, and certainly by RC1. It really does give a much better user experience and better first impression to those updating/installing to get that simpler, more meaningful license dialog. Thanks, ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
