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-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] 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
<igor@xxxxxxxxxxxxxx>
To: cross-project-issues-dev@xxxxxxxxxxx
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-bounces@xxxxxxxxxxx
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@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4569 / Virus Database: 3920/7389 - Release Date: 04/24/14