slachiewicz opened a new issue, #1793:
URL: https://github.com/apache/maven-site/issues/1793

   Martijn Dashorst ran every command of his guide pages on Maven 3.9.16, 
3.10.0 and 4.0.0-rc-7 and listed 48 places where Maven's documentation and 
Maven disagree: 
[discrepancies.md](https://github.com/dashorst/maven-site/blob/diataxis-demo/jekyll/pages/discrepancies.md)
 on the `diataxis-demo` branch of dashorst/maven-site. This issue tracks what 
came of each item. Numbers are his.
   
   ### Fixed in this repository
   
   | Items | Where |
   |---|---|
   | 4, 5, 13, 14, 17, 25, 34, 47 | #1779 |
   | 3 (getting-started samples) | #1781 |
   | 5 (`mvn -v` sample), current versions | #1785 |
   | 6, 19, 26, 27, 28, 33 | #1783 |
   | 15, 16, 18, 20 | #1791 |
   | 21, 22, 23 | #1792 |
   | 37, 38 | already on master |
   
   ### Elsewhere
   
   | Item | Where |
   |---|---|
   | 9 (Maven 4 lifecycle links) | #1655 |
   | 11 (`repositoryOrigins` on Maven 4), 30 (consumer POM) | #1718, #1726 |
   | 22: `mvnenc init` saves `env:null` | apache/maven#13785 |
   | 23: no `<relocation>` in Maven 4's legacy dispatcher | intended, 
codehaus-plexus/plexus-sec-dispatcher#74; documented in #1792 |
   | 24: piped input to `--encrypt-master-password` gives `{}` | fixed for 
3.10.1 in apache/maven#13589 (apache/maven#10230) |
   | 43: POJO tests skipped silently since Surefire 3.6.0 | 
apache/maven-surefire#3566 |
   
   ### Still to check
   
   * Settings and multi-module builds: 12, 29, 31, 32, 35, 36
   * Toolchains: 39, 40 (in this repository), 41 (toolchains plugin), 42 
(Surefire)
   * Other projects: 2 and 8 (archetype), 10 (Resolver message), 44 to 46 
(Shade and jar plugins)
   * Wishes rather than errors: 7 (`src/main/filters` and `src/assembly` in the 
standard layout), 48 (documentation style guide)
   


-- 
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]

Reply via email to