Skip to content

EOL tracking with release date of current dependency version #267

@neifach

Description

@neifach

We are looking for a tool to support EOL management of dependencies.

The current Libyear is great for being aware of possible updates, ensuring that projects don't use real old dependency versions when newer ones are available.

But what if there hasn't been a newer version of a dependency for years? It never shows up because there is no update. We also want to visualize these dependencies so that the project can decide what to do with these old dependencies. Is it still OK to use them or should they be replaced with another dependency? Maybe only the GAV was changed? Or is there a fork? Or something completely new? We want to save such dependencies in a new report file.

An overview of what changes would be required to make this possible:
a) a new optional configuration parameter "reportFile" which contains the path to the new report file.
b) a new configuration parameter "minLibYearsForReport" which contains a minimum age and tells the report to include all dependencies older than "minLibYearsForRep".

Only if the configuration parameter is used in a) will b) be executed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions