[MRELEASE-915] Forked execution of perform leaks source roots
- Dominant language
- Java
- Stars
- 128
- Forks
- 145
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
**[Benson Margulies](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bmargulies)** opened **[MRELEASE-915](https://issues.apache.org/jira/browse/MRELEASE-915?redirect=false)** and commented
https://github.com/bimargulies/release-root-leakage is a test case for the following:
If you add a source root in generate-sources in a pom, that source root will show up in the 'validate' phase in the forked execution for release:perform. This causes checkstyle to see things that it should not, if nothing else bad.
---
**Affects:** 2.5.1
1 votes, 4 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the test case at https://github.com/bimargulies/release-root-leakage and reproduce the issue around release:perform, generate-sources, and the forked validate phase. Trace how source roots carry into the forked execution; done means roots added during generate-sources no longer appear there, so checkstyle does not inspect them unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100