automate consistency checks
Open
- Dominant language
- No language data
- Stars
- 125
- Forks
- 104
- Avg merge
- 2h 24m
- Merged PRs (30d)
- 3
Description
when we add or archive a component, we often forget one of the following:
- repo's default.xml
- README.md
- aggregator build
- dist tool https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/index.html
- sources list https://maven.apache.org/scm.html
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repo's default.xml, README.md, aggregator build, dist tool, and sources list first. Trace how component additions and archivals affect each location and identify the existing build entry points for consistency checks. Done means these locations are checked automatically when components change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100