Temporary configurations (gutter and context runs, Maven tool window goals)
were kept in local storage with what settings derived when they were made:
the absolute mvn, -s / -Dmaven.repo.local and JAVA_HOME. They never went
through the backend again, so after changing the Maven home, settings file or
JDK they, and test runs narrowed from them, still ran the old ones.
They are now kept without the derived values (run_without_derived, the same
stripping saved configurations get) and get the current settings applied when
the run list loads (run_apply_settings), which happens again after a settings
change. Maven's user settings file and local repository now apply to every
Maven configuration, each unless the configuration sets it itself, so they
can be stripped and put back. Entries kept by earlier versions are dropped
once (new storage key).
l0ng-ai
81e4430242