mojohaus/license-maven-plugin

add an option to avoid "remove it from the missing file" in the build log

Open

#201 opened on Jan 11, 2019

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Java (127 forks)auto 404
add-third-partyenhancementhelp wanted

Repository metrics

Stars
 (115 stars)
PR merge metrics
 (PR metrics pending)

Description

In our multi-module project we use the license-plugin with the missingFileUrl option. We created a company-wide missing file which contains GAV and license information for all the dependencies used in our projects for which the license information is not supplied by the dependency itself. So we do not need to gather this information for every single project.

As a result the global missingFile contains more GAV than used in a single project.

This causes the build log to contain a lot of lines with

[08:29:56] [WARNING] dependency [] does not exist in project, remove it from the missing file.

For example for one of the current projects there are 7477 such lines in the build log.

This makes it really hard to find any other information in the build log.

So I would suggest to add an option to decide if this kind of warning should be logged or not.

Or maybe the warning is completely removed or set to debug, because if does not imply any real problem.

Contributor guide

Research direction
Locate the warning message in the source code (search for 'does not exist in project, remove it from the missing file') and add a new configuration property (e.g., 'suppressMissingFileWarnings') to control its output. Update the corresponding documentation and tests.
Tech stack
java
Domain
build system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
MavenJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75