HDDS-11630. Add Build from Maven guide

[ptlrs]

What changes were proposed in this pull request?

Added content for the developer guide to build ozone sources using maven

Please describe your PR in detail:

• Updated the content for building ozone sources using maven
• Added new words to the dictionary to fix the spelling linter

What is the link to the Apache Jira?

https://issues.apache.org/jira/browse/HDDS-11630

How was this patch tested?

CI:
https://github.com/ptlrs/ozone-site/actions/runs/11606635045
https://github.com/ptlrs/ozone-site/actions/runs/11811331336
https://github.com/ptlrs/ozone-site/actions/runs/11823796643
https://github.com/ptlrs/ozone-site/actions/runs/11842696659
https://github.com/ptlrs/ozone-site/actions/runs/11842732645
https://github.com/ptlrs/ozone-site/actions/runs/12627619493
https://github.com/ptlrs/ozone-site/actions/runs/12703203099
https://github.com/ptlrs/ozone-site/actions/runs/12757136988

Ran the website locally via docker-compose:

[errose28]

Thanks for working on this @ptlrs. There's a fair amount of maven options hidden in Ozone that would be good to document here too. We can probably collect input from other devs on what they are using. Some that I have saved:

• Skip pnpm build of Recon front-end: -Dskip.npx=true
• Skip shading Hadoop client jars: -DskipShade

These options greatly speed up the build if you are a developer and know you do not need either of these components.

[errose28]

Let's see if we can finalize this as part of this change as well. The only thing I'm not sure about is the maven version. Really Ozone should define this in its pom probably using something like the Maven enforcer plugin. Maybe we should raise a PR to add this to the main Ozone repo and then update the docs.

[ptlrs]

That's a good point we should take advantage of the enforcer plugin to have reproducible builds.

However, what should be considered the minimum version for Maven and Git? We depend on Hadoop and I can see if they have a minimum version specified for Maven.

On that note, it is also not clear what the minimum version of Java should be. We do build with versions 8, 11, 17. Some of the pom files specify the compiler source and target versions to Java 8. Some of the tests fail when run from the IDE with a newer JDK and need extra JVM parameters to allow Java lang and util modules and the security manager.

[errose28]

See also some updates to the way we skip Recon frontend build in apache/ozone#7454

[errose28]

Thanks for the updates @ptlrs. I left a few more comments but overall flow and content looks pretty good.

[errose28]

Thanks for the updates, just a few comments left

[errose28]

Looks great, thanks for the updates! Just a few minor comments

[ptlrs]

Thank you @errose28 @adoroszlai @jojochuang @smengcl for the reviews.I have made the requested changes.
Could you please take a final look and let me know if there are any changes needed. Thank you.

[adoroszlai]

Thanks for the update.

BTW, you don't need to update the PR description with link to new CI runs from your fork. That link is only important initially, to show that you have a clean run before creating the PR. Once created, the PR triggers its own CI run every time you push new changes.

[ptlrs]

BTW, you don't need to update the PR description with link to new CI runs from your fork. That link is only important initially, to show that you have a clean run before creating the PR. Once created, the PR triggers its own CI run every time you push new changes.

Thanks @adoroszlai. Good to know.

[errose28]

Thanks for the continuous updates @ptlrs LGTM

[adoroszlai]

Thanks @ptlrs for the doc, @errose28, @jojochuang, @smengcl for the reviews.

[ptlrs]

Thank you for the detailed reviews @adoroszlai, @errose28, @jojochuang and @smengcl.