slachiewicz opened a new pull request, #13212: URL: https://github.com/apache/maven/pull/13212
Closes #13211. A parent that an earlier build installed into `.mvn/target/project-local-repo` resolves from the `WorkspaceRepository` because the ReactorReader serves that directory too, so `DefaultProjectBuilder` treated it as a checkout and gave the `MavenProject` a basedir inside the repository. Maven 3 leaves the file unset for any parent that is not in the reactor, and plugins rely on `getBasedir() == null` to look for the parent's attached artifacts instead of its sources (maven-site-plugin's `inheritance-interpolation` IT, apache/maven-site-plugin#1259). The workspace result now counts as a local project only when its POM is the POM of a project in this session; anything else the workspace serves is built like a repository artifact. The issue text blames the `pomFile` the model builder sets on resolved sources. That turned out not to be the path taken: clearing it changes nothing for this case, and a parent from the local repository never goes through the workspace branch. Verified: maven-site-plugin ITs on Maven 4.0.0-SNAPSHOT with this change and doxia-sitetools 2.1.0 → Passed: 62, Failed: 0 (baseline: `inheritance-interpolation` fails); maven-core unit tests → 630 run, 0 failures. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
