Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- is related to
-
MNG-7455 [REGRESSION] IllegalStateException in SessionScope during guice injection in multithreaded build
- Closed
- is required by
-
MNG-7474 SessionScoped beans should be singletons for a given session
- Closed
- relates to
-
MNG-7347 SessionScoped beans should be singletons for a given session
- Closed
- links to