Maven adapter: fewer full-suite fallbacks (tracking issue)

Offen
#89 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java, typescript
Bereich
build-system

Rechercherichtung

Start in src/repo/adapters/maven.ts, where the adapter decides when to record a blockers entry and fall back to the full suite, and read the Maven table in docs/using-diffci.md that lists each fallback. Pick one unchecked step, such as custom sourceDirectory roots, and confirm the current fallback path before changing it. Done means that case no longer falls back, the blocker is gone, and the docs table is updated in the same change.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

adapter enhancement help wanted

DiffCI works out what a change needs from CI, starting with the tests it affects, so AI coding agents (and people) can run them before pushing. Conventional Maven reactors are supported today (src/repo/adapters/maven.ts), but some real Maven repositories still fall back to the full suite. This issue tracks closing those fallbacks, and it's open for contributors and design partners.

Today a Maven repository runs the full suite when it:

  • sets custom source roots (<sourceDirectory> or <testSourceDirectory> other than the defaults)
  • inherits dependencies from an external parent POM
  • uses a ${property} dependency version DiffCI can't resolve
  • has a reactor with no Java sources (resources only)

Steps (each is one PR; take any that are unblocked):

  • Follow custom <sourceDirectory> and <testSourceDirectory> roots
  • Resolve dependencies inherited from an external parent POM (from the local repository, or mvn help:effective-pom output when available)
  • Resolve ${property} versions from the POM chain and -D / .mvn/maven.config
  • Replay on one public Maven repository and publish the report

Gradle is separate: #68.

Ground rules

  • When the adapter is unsure, it records a blockers entry and DiffCI runs the full suite. An empty graph must never look like "nothing affected".
  • Every fallback is listed under "Maven" in docs/using-diffci.md. A PR that removes one updates that table.
  • Discuss design questions here, so every step stays consistent.

Have a Maven repository that falls back today? Run npx --yes @diffci.com/diffci@latest check --base origin/main --head HEAD and post the fallback reason below. Real repositories decide the order.

Vorherrschende Sprache
TypeScript
Sterne
0
Forks
4
Ø Merge
18 Std. 41 Min.
Gemergte PRs (30 T.)
48

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus DiffCI/core

Alle Issues in DiffCI/core

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.