sergehuber opened a new pull request, #840:
URL: https://github.com/apache/unomi/pull/840

   ## Plain-language summary
   
   Unomi’s build still asked old Maven repositories for jars. When those hosts 
were slow or unreachable, CI could burn its full time budget on retries and 
look cancelled even when the code was fine. This change stops using those 
obsolete repositories so builds stay on healthy sources.
   
   ## What changed
   
   * Remove the project-declared Maven repositories from the root POM: 
ServiceMix SVN m2-repo, OPS4J Sonatype snapshots (404), and the redundant 
Apache snapshots-group URL.
   * Keep resolution on repositories already provided by the Apache parent POM: 
Maven Central and Apache snapshots.
   * Leave a short comment pointing at UNOMI-971 so the reason stays visible.
   
   ## Decision record (ticket outcome)
   
   | Repository | Action | Why |
   |---|---|---|
   | ServiceMix SVN m2-repo | Removed | Obsolete since ~2015; stalled 
`karaf:verify` / CI (same as CAMEL-12474 / KARAF-5294) |
   | OPS4J Sonatype snapshots | Removed | URL returns 404; Unomi uses released 
Pax/OPS4J artifacts from Central |
   | Apache snapshots-group (project) | Removed | Redundant with parent 
`apache.snapshots` |
   | Parent Apache snapshots + Central | Kept | Still required / default |
   
   ## Test plan
   
   - [x] Effective POM: only `apache.snapshots` + `central` (no `servicemix` / 
`ops4j-snapshots` repo URLs)
   - [x] `./build.sh --ci` — BUILD SUCCESS; `karaf:verify` logs `Using 
repositories: …/snapshots, …/maven2` only
   - [x] `./build.sh --ci --integration-tests --no-clean` (Elasticsearch) — 
**307/307** failsafe tests, 0 failures/errors (~28 min)
   - [ ] OpenSearch IT suite (running locally / covered by GitHub Actions 
matrix)
   - [ ] GitHub Actions: Build and run tests (unit + ES/OS ITs)
   
   ## References
   
   UNOMI-971, CAMEL-12474, KARAF-5294


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to