The org.eclipse.license question was kind of a stupid one I must
admit. I'm well aware of the CBI repository, using it as the
basis against which to validate license correctness, but I got
completely sidetracked thinking this thing used by the platform
must from some platform repository. Silly me, and thanks for all
the friendly help on that one!
__________________________
As a follow up question. Where do the platform's products come
from? I can't find any corresponding .product files.
The reason I ask is that the only valid licenses in the
platform's p2 repos are the ones that come from EMF and ECF. All
other licenses are corrupted in some way. This naturally leads to
the assumption that this is something that Oomph can fix or
address:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=549523
But it is not something I can fix. It must be fixed at the
source of the bad license.
I believe I tracked down the source of most of the bad licenses
in the platform's repos, but not for the products; these have yet
two more different variants of the SUA 2.0.
If someone could enlighten me on where the products come from,
then I'll be able to make progress to eliminate at least this one
source of end-user annoyance.
Regards,
Ed
On 24.08.2019 12:59, Vikas Chandra
wrote:
>>if anyone uses
other ways to solve such a puzzle. :)
How about searching for org.eclipse.license
eclipse git repo
and then clicking on the 1st link?
Regards,
Vikas
----- Original message -----
From: Michael Keppler <Michael.Keppler@xxxxxx>
Sent by: platform-dev-bounces@xxxxxxxxxxx
To: platform-dev@xxxxxxxxxxx
Cc:
Subject: [EXTERNAL] Re: [platform-dev] Where Does
org.eclipse.license Come From?
Date: Sat, Aug 24, 2019 4:16 PM
Am 23.08.2019 um 11:30 schrieb Ed
Merks:
> Does anyone know where I might find it? I'd be ever
so grateful for a
> pointer!
Ed, you recently taught us to use the eclipse.org index
for finding the
sources of Java types. It can help with that question,
too.
Using the "Discover provided capabilities" dialog from the
Oomph
repository browser with the input "org.eclipse.license" we
can find jars
with the URL
http://download.eclipse.org/cbi/updates/license/2.0.2-SNAPSHOT and
similar, pointing us to the "cbi" project.
Given that information, we can ask gerrit to find
"org.eclipse.license"
in repositories related to "cbi":
https://git.eclipse.org/r/#/q/projects:cbi+org.eclipse.license.
That
shows several related source changes.
Of course I would like to know if anyone uses other ways
to solve such a
puzzle. :)
Ciao, Michael
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________