slachiewicz opened a new pull request, #1783: URL: https://github.com/apache/maven-site/pull/1783
Documents behaviour that Martijn Dashorst found undocumented while running the guides ([discrepancies.md](https://github.com/dashorst/maven-site/blob/diataxis-demo/jekyll/pages/discrepancies.md), items 6, 19, 26, 27, 28 and 33): - Both multi-module guides: a parent that is part of the build is sorted before its children; a bare `-pl` name is a path, `:artifactId` selects by artifactId; `--fail-never` still reports `BUILD FAILURE` but exits with 0 and still tries to build the dependents of a failed module. The Maven 3 guide also gains `--projects` and `--fail-never`; the Maven 4 guide notes that Maven 3 does not support the `?` prefix. - *Configuring Apache Maven*: `#` comments in `.mvn/jvm.config` work only on Maven 4; Maven 3 fails with `Could not find or load main class #`. - *Introduction to the Build Lifecycle*: the warning that `mvn integration-test` leaves the container running holds for Maven 3; Maven 4 also runs the `after:` phase, linked to *What's new in Maven 4*. Verified on Maven 3.9.16, 3.10.0 and 4.0.0-rc-7 with a small reactor (parent listed last, module directory `core` with artifactId `shop-core`, a failing module and a dependent): build order, `-pl core`/`-pl shop-core`/`-pl :shop-core`, `-pl ?:missing`, `-fn` exit code, a `#` line in `jvm.config`, and `mvn integration-test` with goals bound to `pre-`/`post-integration-test` (3.9.16 runs only `pre-`, 4.0.0-rc-7 both). `mvn site` with Fluido 2.1.0 → no URL or content anchor lost. -- 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]
