[
https://issues.apache.org/jira/browse/MRESOLVER-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-535:
--------------------------------------
Summary: DependencyGraphDumper should be configurable (was:
DependenctGraphDumper should be configurable)
> DependencyGraphDumper should be configurable
> --------------------------------------------
>
> Key: MRESOLVER-535
> URL: https://issues.apache.org/jira/browse/MRESOLVER-535
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-11
>
>
> In a sense, we just accumulate what all it prints out (see class history),
> but this should be in fact somehow configurable.
> Maybe refactor all the output into "decorator" (appender)? And the let ctor
> just accept a collection of them (with some predefined collections for some
> defaults)? As then, user/caller is fully in charge what the dumper is writing
> out, plus, is extensible with original "decorator" idea.
> Original decorator idea was that I had a lookup table of some "extra info",
> and decorator was basically appending info from that lookup table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
