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

Abierto
#89 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java, typescript
Área
build-system

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
4
Merge medio
18 h 41 min
PR fusionados (30 d)
48

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DiffCI/core

Todos los issues de DiffCI/core

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.