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

Aberta
#89 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, typescript
Domínio
build-system

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
0
Forks
4
Merge médio
18h 41min
PRs com merge (30d)
48

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de DiffCI/core

Todas as issues de DiffCI/core

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.