[MNG-8576] Investigate modifying the Toolchain API to be session/project scoped

[jira-importer]

Guillaume Nodet opened MNG-8576 and commented

We do underuse the scopes as we tend to pass the Session in all requests to have stateless services.

The ToolchainManager is a good example, as we do actually get the mojo execution context to get to the project and store/retrieve the selected Toolchain according to that.

That looks wrong and should be simplified.

---

Affects: 4.0.0-rc-3

Issue Links:

• MNG-8558 Switch DefaultToolchainManager to Api V4

[goutamadwant]

@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.