Maven: follow a custom `<testSourceDirectory>`
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 68/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- build-system, testing
调研方向
Start in src/repo/adapters/maven.ts and inspect how custom source roots trigger the full-validation blocker. Find the Maven adapter tests and synthetic fixtures under tests/repo/, then add cases for a resolvable custom test root, a custom source root, and an unresolved or outside-module test root. Run npm test; done means only the resolvable test-root case avoids fallback, while the other two still fall back for the stated reason.
由索引模型根据 Issue 内容生成。
描述
Part of #89 (the "Follow custom <sourceDirectory> and <testSourceDirectory> roots" step), split out so it can be done on its own.
Today any custom source root makes the Maven adapter fall back to the full suite: src/repo/adapters/maven.ts sets customSourceRoots when a POM's <sourceDirectory> isn't src/main/java or its <testSourceDirectory> isn't src/test/java, and that adds the blocker Maven <pom>: custom source roots require full validation.
The test root alone is the smaller half: it only changes where tests are found, not how modules depend on each other.
Done when:
- A module whose only customization is
<testSourceDirectory>finds its tests there and no longer falls back for that reason. - A custom
<sourceDirectory>still falls back, with the same reason as today. - A
<testSourceDirectory>the adapter can't resolve with certainty (a property such as${project.basedir}/..., or a path outside the module) still falls back. Never guess. - There are synthetic Maven fixtures under
tests/repo/for each case above.
maven.ts is 128 lines. This is a step up from a good first issue: it suits someone who has already merged a PR or two here.
See CONTRIBUTING.md: add a synthetic fixture, run npm test, and sign off commits with git commit -s. Comment here to claim the issue.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 4
- 平均合并
- 18 小时 41 分钟
- 30 天内合并 PR
- 48
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
DiffCI/core 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at random可能已有人在做 @FredApps 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
Agent tools: changed_files lists only the new path of a renamed file可能已有人在做 @FredApps 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
adapter good first issue
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
相似的 Issue
-
agent-ready area: ui-server priority: p3 type: test
难度 2/5 1-3 小时 新手友好度 78/100
schlessera/brain-kit#4249 ·
维护者通常 1 天内回复
-
documentation tool triaged
难度 2/5 1-3 小时 新手友好度 73/100
can1357/oh-my-pi#19608 · 2 条评论 ·
维护者通常 1 天内回复
-
dependencies tech-debt
难度 2/5 1-3 小时 新手友好度 65/100
bcgov/nr-waste-plus#1549 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 78/100
blixvip/solana-tx-parse#18 ·