Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-7401

Make MavenSession#getCurrentProject() using a thread local

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 3.9.0, 4.0.0-alpha-2, 4.0.0
    • 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

          Activity

            People

              gnodet Guillaume Nodet
              laeubi Christoph Läubrich
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: