Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] dependencies and CQs - best practices and tooling

Hi Mickael,


I quote from a post of Wayne Beaton on the ‘incubation’ list (subject was “[incubation] IP policy for transitive dependencies”):

“All content must be taken through the Eclipse IP Due Diligence Process. This includes all dependencies, dependencies of dependencies, etc. [recursive].”




BTW: I can’t seem to find the ‘incubation’ list on


Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mickael Istria
Gesendet: Donnerstag, 16. August 2018 11:59
An: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Betreff: Re: [cross-project-issues-dev] dependencies and CQs - best practices and tooling




On Fri, Aug 10, 2018 at 5:40 PM, Henrik Rentz-Reichert <hrr@xxxxxxxxx> wrote:

·        I found a hint that Maven can print dependencies [1] and used this in a Jenkins job that I’ve created for this purpose [2]. A post build step greps the interesting lines, sorts them unique and prints the result to the console (see [6] for an example).


Listing dependencies with maven also includes transitive dependencies that are usually not shipped by your project as they are either pre-installed or coming transitively from another source. In such case, you don't need a CQ for them. Only dependencies you 1. directly rely on or 2. ship in your deliverables should require a CQ if I'm not mistaken.

Diese Nachricht wurde mit einer kostenlosen Version von Proxy-Manager gesendet.
Wollen Sie von Ihrem Exchange-Konto mit einer Ihrer Proxy SMTP-Adressen senden?
Testen Sie Proxy-Manager kostenlos!

Diese Fußzeile wird nicht in der registrierten Version von Proxy-Manager angezeigt.
Klicken Sie hier, um Proxy-Manager zu registrieren.

Back to the top