Check build.xml files to ensure they fail fast when one of their targets fail
Open
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
This came up in context of JavaTestUtil.java failed to compile, but we continued on to try and run tests. See: https://github.com/adoptium/aqa-tests/blob/master/jck/build.xml
We should check all build.xml files in this repo and add failonerror="true" in targets that need it, much like was done in https://github.com/adoptium/aqa-tests/pull/2179
Contributor guide
Research direction
Start with jck/build.xml and compare its target error handling with the approach used in pull request 2179. Inventory the repository's build.xml files, identify targets that should stop after a failure, and verify that a failed compilation or test target prevents later targets from running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100