Joakim:
It is my understanding that these files are generated, based on
the third party contribution details, which we submit as part of
the initial contribution. Prior to submission, the dependencies
were generated from Maven dependency analysis reports and may
include direct and indirect dependencies.
Committers can search the ipzilla bug database to determine if
the dependencies do, or do not match what has been recorded in
Eclipse back-end IP catalog. For example, All WebSocket IP details
can be viewed by searching for the component: ee4j.websocket
That list includes:
- 16060
- Google Guava Version: 18.0 (PB Orbit CQ12184)
- 16061
- atinject (Package javax.inject) Version: 1.0 (PB Orbit CQ3578)
- 16062
- javax.validation:validation-api:jar:1.1.0.Final (PB CQ15114
Type A)
It is plausible this is a mistake, but let's see what the
committer says (Roman Grigordi) before taking any action. I agree,
there is a bit of a question because in the initial CQ, Roman
indicates there are no third party dependencies (see 15333).
I'm not sure where these came into the picture.
In short, I think the idea is that the NOTICE file should be
generated properly. I don't have enough experience to say if, once
it's generated -- can it be updated. If it is frequently
regenerated, adding custom text might be a problem. Let's see what
Roman says about these.
Thanks!
-- Ed
On 9/19/2018 3:25 PM, Joakim Erdfelt
wrote:
The websocket-api project is in the process of bringing
in the various "legal documents" that the wiki mentions at
..
However, the generated NOTICE file is a bit off,
especially in the section for "Third-party Content".
Are the individual projects free to update the
"Third-Party Content" section of the NOTICE file on their
own?
Or do we need to get approval from the legal groups at
either the ee4j-pmc or Eclipse Foundation for any proposed
changes first?
Thanks,
- Joakim Erdfelt
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build