Mapped dependency ${dependency.group}${dependency.name} to ${dependencyName} for license info – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Mapped dependency ${dependency.group}${dependency.name} to ${dependencyName} for license info ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task.

Log Context

Log “mapped dependency ${dependency.group}:${dependency.name} to ${dependencyName} for license info” classname is DependenciesInfoTask.groovy.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 continue
            }

            final String url = createURL(dependency.group; dependency.name; dependency.version)
            final String dependencyName = DependencyLicensesTask.getDependencyName(getMappings(); dependency.name)
            logger.info("mapped dependency ${dependency.group}:${dependency.name} to ${dependencyName} for license info")

            final String licenseType = getLicenseType(dependency.group; dependencyName)
            output.append("${dependency.group}:${dependency.name};${dependency.version};${url};${licenseType}\n")

        }




 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content