[
https://issues.apache.org/jira/browse/MNG-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805122#comment-17805122
]
ASF GitHub Bot commented on MNG-7999:
-------------------------------------
cstamas commented on code in PR #1367:
URL: https://github.com/apache/maven/pull/1367#discussion_r1447349763
##########
maven-core/src/main/java/org/apache/maven/internal/impl/DefaultLookup.java:
##########
@@ -24,6 +24,8 @@
Review Comment:
Perso, I'd even move Lookup service to "internal service" (like CoreRealm
is), not exposing it to plugins. It serves a very good purpose in Core (to hide
Plexus), while plugins can achieve all these with plain JSR330 (or Maven
specific JSR330-like annos if they become to existence once).
> Confine Plexus as much as possible, switch to Lookup
> ----------------------------------------------------
>
> Key: MNG-7999
> URL: https://issues.apache.org/jira/browse/MNG-7999
> Project: Maven
> Issue Type: Task
> Components: Core
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-11
>
>
> Confine plexus use in core as much as possible. Probably almost all uses may
> be replaced with API Lookup.
> Cleanup unused members as well, I found at least two components:
> * org/apache/maven/lifecycle/DefaultLifecycleExecutor
> * org/apache/maven/lifecycle/internal/LifecycleStarter
> but I bet there are more...
> Given clients should _inject_ and not manually instantiate components, ctor
> changes should be hidden from them (managed by DI). Hence, changes like these
> are "safe" as long as client code "plays by the rules".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
