Commit c2282cd
Fix cache warmer: run real test to resolve surefire provider (#1385)
## Summary
The cache warmer was not caching `surefire-junit-platform:3.1.2` because
surefire resolves its provider JAR lazily at test execution time, not at
plugin initialization. The previous approach (`-Dtest=NoSuchTest`)
failed before surefire downloaded the provider.
Fix: run a real lightweight test
(`DatabricksParameterMetaDataTest#testInitialization`) to force full
surefire provider resolution.
### Verified locally
All 4 previously missing artifacts are now in the local cache after
running the test:
- `surefire-junit-platform:3.1.2` (blocked unit-tests + integration
tests)
- `maven-toolchains-plugin:3.2.0` (blocked unit-tests)
- `maven-clean-plugin:3.2.0` (blocked coverage)
- `exec-maven-plugin:1.2.1` (blocked coverage)
The 5 maven-metadata.xml warnings are non-blocking (Maven falls back to
cached plugin JARs).
## Test plan
- [x] Verified locally: `mvn -pl jdbc-core test
-Dtest="DatabricksParameterMetaDataTest#testInitialization"` passes and
resolves all missing plugins
- [ ] After merge: re-trigger cache warmer on main, then re-run PR #1371
CI
NO_CHANGELOG=true
This pull request was AI-assisted by Isaac.
---------
Signed-off-by: Gopal Lal <gopal.lal@databricks.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>1 parent 77f8c84 commit c2282cd
1 file changed
+7
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
142 | 142 | | |
143 | 143 | | |
144 | 144 | | |
145 | | - | |
146 | | - | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
147 | 150 | | |
148 | 151 | | |
149 | 152 | | |
150 | 153 | | |
| 154 | + | |
151 | 155 | | |
152 | | - | |
| 156 | + | |
153 | 157 | | |
154 | 158 | | |
155 | 159 | | |
| |||
0 commit comments