Rolf,
No, I mean the platform's own products. There are five of them:
If I search for "Eclipse Platform SDK" in my platform SDK workspace,
there are no matching strings. I looked through the "platform" repos in
https://git.eclipse.org/c/ (that aren't already in my workspace) but I
can find nothing that seems related there. So I cannot figure out where
the following IUs originates, not even the text for its name, and most
especially not the corrupted license text:
<unit id='org.eclipse.platform.sdk' version='4.13.0.I20190607-0725'>
<update id='org.eclipse.platform.sdk'
range='[4.0.0,4.13.0.I20190607-0725)' severity='0' description='An
update for 4.x generation Platform SDK'/>
<properties size='5'>
<property name='org.eclipse.equinox.p2.name' value=*'Eclipse
Platform SDK*'/>
*<property name='org.eclipse.equinox.p2.type.product' value='true'/>*
<property name='org.eclipse.equinox.p2.type.group' value='true'/>
<property name='org.eclipse.equinox.p2.description' value='4.12
Release of the Platform SDK.'/>
<property name='org.eclipse.equinox.p2.provider' value='Eclipse.org'/>
</properties>
<provides size='1'>
<provided namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.platform.sdk' version='4.13.0.I20190607-0725'/>
</provides>
<requires size='12'>
<required namespace='org.eclipse.equinox.p2.iu'
name='toolingorg.eclipse.platform.sdk.application'
range='[4.13.0.I20190607-0725,4.13.0.I20190607-0725]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='tooling.org.eclipse.update.feature.default' range='[1.0.0,1.0.0]'>
<filter>
(org.eclipse.update.install.features=true)
</filter>
</required>
<required namespace='org.eclipse.equinox.p2.iu'
name='toolingorg.eclipse.configuration.macosx' range='[1.0.0,1.0.0]'>
<filter>
(osgi.os=macosx)
</filter>
</required>
<required namespace='org.eclipse.equinox.p2.iu'
name='tooling.source.default' range='[1.0.0,1.0.0]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='toolingorg.eclipse.platform.sdk.configuration'
range='[4.13.0.I20190607-0725,4.13.0.I20190607-0725]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='toolingorg.eclipse.configuration' range='[1.0.0,1.0.0]'>
<filter>
(!(osgi.os=macosx))
</filter>
</required>
<required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.platform.feature.group'
range='[4.13.0.v20190607-0954,4.13.0.v20190607-0954]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.equinox.p2.user.ui.source.feature.group'
range='[2.4.400.v20190516-1504,2.4.400.v20190516-1504]'/>
<required namespace='osgi.ee' name='JavaSE' range='0.0.0'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.equinox.p2.user.ui.feature.group'
range='[2.4.400.v20190516-1504,2.4.400.v20190516-1504]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='tooling.osgi.bundle.default' range='[1.0.0,1.0.0]'/>
<required namespace='org.eclipse.equinox.p2.iu'
name='org.eclipse.platform.source.feature.group'
range='[4.13.0.v20190607-0954,4.13.0.v20190607-0954]'/>
</requires>
<touchpoint id='org.eclipse.equinox.p2.osgi' version='1.0.0'/>
<touchpointData size='1'>
<instructions size='1'>
<instruction key='configure'>
addRepository(type:0,location:http${#58}//download.eclipse.org/eclipse/updates/4.13,name:The
Eclipse Project
Updates);addRepository(type:1,location:http${#58}//download.eclipse.org/eclipse/updates/4.13,name:The
Eclipse Project
Updates);addRepository(type:0,location:http${#58}//download.eclipse.org/releases/2019-09,name:2019-09);addRepository(type:1,location:http${#58}//download.eclipse.org/releases/2019-09,name:2019-09);mkdir(path:${installFolder}/dropins);
</instruction>
</instructions>
</touchpointData>
<licenses size='1'>
<license uri='http://eclipse.org/legal/epl/notice.php'
url='http://eclipse.org/legal/epl/notice.php'>
*<!-- long bad license here -->*
</license>
</licenses>
</unit>
On 24.08.2019 13:51, Rolf Theunissen wrote:
"the platform products" are you referfing the the EPP packages?
In that case:
https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git
At least a quick check shows that they do not mention EPL 2.0 yet.
Regards,
Rolf
Op za 24 aug. 2019 om 13:28 schreef Ed Merks <[email protected]
<mailto:[email protected]>>:
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 <[email protected]>
<mailto:[email protected]>
Sent by: [email protected]
<mailto:[email protected]>
To: [email protected] <mailto:[email protected]>
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
<http://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
[email protected] <mailto:[email protected]>
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
[email protected] <mailto:[email protected]>
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
[email protected] <mailto:[email protected]>
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
[email protected]
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
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
