Skip to content

Better logic to populate metadata.component.components #394

Open
@prabhu

Description

@prabhu

The logic to populate parentSubComponents needs to be refactored since the dependency tree generated for large monorepos has dangling parents. With 9.2.x, we throw warnings in DEBUG_MODE for missing refs to address these over time.

Example warning:

===== WARNINGS =====
[
  'Version is missing for metadata.component with ref pkg:application/struts-6.1.2.1'
]
===== WARNINGS =====
[
  'Invalid ref in dependencies pkg:maven/org.apache.struts/[email protected]?type=pom',
  'Invalid ref in dependencies pkg:maven/org.apache.struts/[email protected]?type=pom',
  'Invalid ref in dependencies pkg:maven/org.apache.struts/[email protected]?type=pom',
  'Invalid ref in dependencies pkg:maven/org.apache.struts/[email protected]?type=pom'
]

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions