[SUREFIRE-1679] Prevent classpath caching from causing pollution#243
[SUREFIRE-1679] Prevent classpath caching from causing pollution#243Tibor17 merged 1 commit intoapache:masterfrom
Conversation
|
@wilkinsona |
|
The build is currently running |
|
@wilkinsona |
|
@wilkinsona |
cae2550 to
65b8965
Compare
|
Oops. Sorry. I've force-pushed a fix for that. I'll take a look at unit tests shortly. Given that the old |
|
@wilkinsona |
65b8965 to
9d497ec
Compare
Previously, classpath caching was performed statically. This resulted in the classpath cached by one project for a particular provider being used by a subsequent project. As a result any customizations to the classpath, such as removing duplicate artifacts, would leak out and pollute the classpath used by subsequent projects. This commit prevents the pollution by making the classpath cache instance-scoped so that the cache is only used by a single mojo and, therefore, a single project.
9d497ec to
0cf43c9
Compare
|
I've force-pushed the switch to a |
|
@wilkinsona |
|
@wilkinsona Thx for contributing! |
|
My pleasure. Thanks for the review and merge. I'd like to work on an equivalent 2.22.x fix now. What branch should I use as the base for that? |
|
iirc, it's this branch https://github.com/apache/maven-surefire/tree/release/2.22.2 |
|
Resolve #2092 |
This PR should fix SUREFIRE-1679. Once the changes have been reviewed and approved, I'll open another PR to backport them to 2.x.