Skip to content
This repository was archived by the owner on Dec 20, 2022. It is now read-only.
This repository was archived by the owner on Dec 20, 2022. It is now read-only.

Warning messages of the maven plugin are not providing enough details to enable efficient investigation #57

Open
@rmlekus

Description

@rmlekus

When applying a scan for licenses using the maven LicenseScout plugin by starting of with the sample configuration a typical maven output contains numerous warning and info messages like:

[WARNING] No license text for license ID: 'NLIL'

Comment: NLIL seems to be a place holder license identifier for "no license information found" in licenses.xml#L6235

[WARNING] Cannot find provider with ID: ''
[WARNING] License not found by URL: https://www.eclipse.org/legal/epl-2.0/, http://www.gnu.org/copyleft/gpl.html, http://www.gnu.org/licenses/lgpl.html
[WARNING] Neither license name nor license URL mapping found for name/URL: Eclipse Public License - v 2.0 / https://www.eclipse.org/legal/epl-2.0/
[WARNING] Parameter buildUrl not configured
[WARNING] Parameter licenseReportHtmlUrl not configured
[WARNING] Parameter licenseReportCsvUrl not configured
[WARNING] Parameter licenseReportTxtUrl not configured
[INFO] No license mapping found for URL: http://www.jooq.org/inc/LICENSE.txt

Bug report

Expected Behavior - What where you expecting to happen?

  1. Warning and Info Levels should be used consistently (see above example 1-5 vs. 6)
  2. Warnings should be classified into
    • Problems in configuration of the project to be scanned by LicenseScout (missing properties, configurations in the pom.xml)
    • Problems or inconsistencies in existing configuration files (e.g. NLIL license text not configured)
    • Missing entries into specific license configuration files, e.g. name or URL mappgins
      (including the file name + maven coordinates configured for the specific license scan
  3. Warnings should always refer to the location in the analysed project (dependencies)

Current Behavior - What happens?

Warnings are generated, but in order to identify the next steps to clarify the problems the source code of the plugin or even java debugging of the maven build process is required to identify the affected project and license scout artifacts.

Possible Solution

  • Check for Log Level to be used: Info/Warning/Error
  • Check for common Warning format: e.g.
    : ; Configuration File

Metadata

Metadata

Assignees

No one assigned

    Labels

    Prio: MediumMedium PriorityStatus: AcceptedIssue or PR is acceptedType: FeatureIssue or PR is a new featurehelp wantedWe are looking for contributors for this issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions