You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/04/26 11:11:00 UTC
[jira] [Updated] (MRESOLVER-542) Reduce usage of final classes
[ https://issues.apache.org/jira/browse/MRESOLVER-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak updated MRESOLVER-542:
--------------------------------------
Description:
Historically, Resolver APIs were exposed via Maven (were kinda part of Maven API in Maven3) and they went long run to keep boundaries what users can do. One of these examples is overuse of `final` classes.
Main goal was to make GenericVersionScheme not final, also perform some cleanup.
was:Historically, Resolver APIs were exposed via Maven (were kinda part of Maven API in Maven3) and they went long run to keep boundaries what users can do. One of these examples is overuse of `final` classes.
> Reduce usage of final classes
> -----------------------------
>
> Key: MRESOLVER-542
> URL: https://issues.apache.org/jira/browse/MRESOLVER-542
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0, 2.0.0-alpha-11
>
>
> Historically, Resolver APIs were exposed via Maven (were kinda part of Maven API in Maven3) and they went long run to keep boundaries what users can do. One of these examples is overuse of `final` classes.
> Main goal was to make GenericVersionScheme not final, also perform some cleanup.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)