-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MNG-7347] SessionScoped beans should be singletons for a given session #621
Conversation
maven-core/src/main/java/org/apache/maven/lifecycle/internal/LifecycleModuleBuilder.java
Show resolved
Hide resolved
maven-core/src/main/java/org/apache/maven/lifecycle/internal/LifecycleModuleBuilder.java
Show resolved
Hide resolved
maven-core/src/main/java/org/apache/maven/lifecycle/internal/ReactorContext.java
Show resolved
Hide resolved
maven-core/src/main/java/org/apache/maven/session/scope/internal/SessionScope.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix version contains 3.8.5, but tests require Java 8. How is this supposed to be backported?
Let me provide a PR for 3.8.5. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Accepting this for master only.
Running ITs... |
Passes for me. |
Related to
The original scopes were working correctly but did not support multithreaded builds.
The new scope implementation does not use threading at all, so it's safer in a multithreaded build.
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MNG-XXX] - Fixes bug in ApproximateQuantiles
,where you replace
MNG-XXX
with the appropriate JIRA issue. Best practiceis to use the JIRA issue title in the pull request title and in the first line of the
commit message.
mvn clean verify
to make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.