[jira] [Created] (MNG-7401) Make MavenSession#getCurrentProject() using a thread local

["Christoph Läubrich (Jira)" <ji...@apache.org>]

Christoph Läubrich created MNG-7401:
---------------------------------------

             Summary: Make MavenSession#getCurrentProject() using a thread local
                 Key: MNG-7401
                 URL: https://issues.apache.org/jira/browse/MNG-7401
             Project: Maven
          Issue Type: Improvement
            Reporter: Christoph Läubrich


I noticed that a session is often cloned due to change the current project for a while.

As this works for everyone passing down the session, consumers of the "upper session" (e.g. a SessionScoped Component) would never see this if they are (indirectly) called and e.g. use Session#getCurrentProject().

I wonder if MavenSession could simply use a ThreadLocal for the currentProject (that is shared accross all cloned sessions), that way one would always get the correct value.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)