[
https://issues.apache.org/jira/browse/MRESOLVER-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277372#comment-17277372
]
Michael Osipov commented on MRESOLVER-163:
------------------------------------------
Your idea is just another physical for them to avoid spreading?
> Introduce "configuration" or "feature" helper to centralize various
> flags/params/configs
> ----------------------------------------------------------------------------------------
>
> Key: MRESOLVER-163
> URL: https://issues.apache.org/jira/browse/MRESOLVER-163
> Project: Maven Resolver
> Issue Type: Task
> Components: Demo, Resolver
> Reporter: Tamás Cservenák
> Priority: Major
>
> Currently we have all kind of {{aether...}} keyed properties (see
> https://maven.apache.org/resolver/configuration.html) available to configure
> Maven Resolver behaviour.
> Bad1: they are spread across codebase
> Bad2: it is not always clear, is it sourced from session or system property
> or both
> So, I'd propose to MOVE all these keys (and probably their handling (reading)
> code into here as well, so we could have
> Good1: all these keys would be listed at one place (easier to document,
> check, etc)
> Good2: simply, one class introspection (reading by dev) would tell all the
> story of it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
