|Re: [cross-project-issues-dev] dependencies and CQs - best practices and tooling|
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 https://www.eclipse.org/forums/
Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mickael Istria
On Fri, Aug 10, 2018 at 5:40 PM, Henrik Rentz-Reichert <hrr@xxxxxxxxx> wrote:
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