slachiewicz opened a new pull request, #1795: URL: https://github.com/apache/maven-site/pull/1795
Items 29 and 32 of #1793. * *Guide to Working with Multiple Subprojects in Maven 4*: the last row of the selection table runs `mvn compile && mvn jetty:run -f subproject-c/subproject-c-2`. With `-f`, Maven 4 resolves the other subprojects from the project-local repository `.mvn/target/project-local-repo`, which only `package` and later phases fill, so after `compile` the dependencies cannot be resolved. The row now uses `mvn package`, and a paragraph under the table explains the project-local repository. * *POM Reference*, inheritance: adds the `../pom.xml` default, the coordinate check on the POM found there, and what an empty `<relativePath/>` does on each line. Verified with a parent, `lib` and `app` depending on `lib`, on 4.0.0-rc-7: `mvn compile` then `mvn -f app compile` → could not resolve `lib`; `mvn package` then `mvn -f app compile` → BUILD SUCCESS; `mvn clean` empties the project-local repository and `-f app` fails again. `<relativePath/>` → 3.10.0 "Non-resolvable parent POM", 4.0.0-rc-7 BUILD SUCCESS; a `<parent>` whose coordinates do not match `../pom.xml` → 3.10.0 "points at demo:parent instead of demo:other-parent", and both lines then search the repositories. Not changed: item 31 (4.0.0-rc-7 also accepts `<parent/>` in a 4.0.0 POM) stays undocumented, since such a POM cannot be built with Maven 3. -- 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]
