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


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.

Back to the top