[MNG-6753] MavenMetadataSource should not use ProjectBuilder
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** opened **[MNG-6753](https://issues.apache.org/jira/browse/MNG-6753?redirect=false)** and commented
While working on MNG-6656 and analyzing which files will be transformed, I noticed that maven-surefire-plugin showed additional pom transformations. This is unwanted, only the reactor poms should be transformed
Root cause is the MavenMetadataSource, which is using the ProjectBuilder to assemble a ProjectRelocation. Having the effectiveModel should be more than enough.
---
**Issue Links:**
- [MNG-6656](https://issues.apache.org/jira/browse/MNG-6656) Introduce base for build/consumer process
Contributor guide
Research direction
Start by inspecting MavenMetadataSource and how it uses ProjectBuilder to assemble a ProjectRelocation, then compare that path with the available effectiveModel. Reproduce the behavior while analyzing maven-surefire-plugin and reactor POM transformations; done means only reactor POMs are transformed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100