goutamadwant commented on issue #10657: URL: https://github.com/apache/maven/issues/10657#issuecomment-5612151831
@gnodet I can take this on. The current manager already stores selected toolchains per project in session data, but still finds the project through `Lookup`. Changing the service scope alone would not remove that coupling. Would a session-scoped manager exposing an explicit project-bound view fit your intent, or would you prefer a directly injected project-bound service? I lean toward the former, retaining the existing `Session`-taking methods as compatibility adapters and making project selection explicit in the new API. I'd test independent toolchain selections across parallel modules, successive sessions, and the compatibility path. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
