From dd81b161fc148f4f103c85db13e5d89c5f975ee7 Mon Sep 17 00:00:00 2001 From: Chapman Flack Date: Thu, 11 Apr 2024 15:11:23 -0400 Subject: [PATCH] Document how to confirm Maven uses the right Java Issues #375 and #385 were closed as, essentially, pilot error (running Maven on a different version of Java than intended), but it would probably help to document that mvn --version does report the Java version Maven is using, so that can be easily checked. --- src/site/markdown/build/build.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/site/markdown/build/build.md b/src/site/markdown/build/build.md index d48103354..df5af711e 100644 --- a/src/site/markdown/build/build.md +++ b/src/site/markdown/build/build.md @@ -60,7 +60,13 @@ There is a "troubleshooting the build" section at the end of this page. mvn --version - succeeds. + succeeds. It reports not only the version of Maven, but the version of Java + that Maven has found and is using, which must be a Java version supported + for building PL/Java (see more on [version compatibility](versions.html)). + If Maven is not finding and using the intended Java version, the environment + variable `JAVA_HOME` can be set to point to the desired Java installation, + and `mvn --version` should then confirm that the Java being found is the + one intended. If you have more than one version installed of PostgreSQL, Java, or the compile/link tools, make sure the ones found on your search path are the