Remove more pre-PL/Java-1.6 remnants from docs

The build system introduced in 1.6 fixed the "Windows might
get -Dpljava.libjvmdefault wrong" issue. Also, by no longer
trying to capture compiler/linker messages and classify them,
it has fixed the "Not all [ERROR]s are errors" issue.

In 1.6, both the pljava and pljava-api jars must be present
in $SHAREDIR/pljava at runtime. So a package maintainer may
choose to include the API jar additionally in a -devel package
that places it where users' development tools will expect, but
may not omit it from the base package that installs it where
the runtime needs it.

Author: jcflack

src/site/markdown/build/build.md

@@ -222,30 +222,6 @@ build issues that are commonly asked about.*
 
 [btwp]: https://github.com/tada/pljava/wiki/Build-tips
 
-#### Not all `[ERROR]`s are errors
-
-In the part of the build that compiles the native code, you may see lines of
-output starting with `[ERROR]`, but the build completes and shows success for
-all subprojects.
-
-Maven is capturing output from the C compiler and adding a tag at the front of
-each line. If the line from the C compiler contains the string `warning:` then
-Maven adds a `[WARNING]` tag at the front of the line; otherwise it adds
-`[ERROR]`. That is how Maven can turn a multiple-line warning, like
-
-```
-type/String.c: In function 'String_createJavaString':
-type/String.c:132:43: warning: conversion to 'jlong' from 'Size' may change
-                      the sign of the result [-Wsign-conversion]
-   bytebuf = JNI_newDirectByteBuffer(utf8, srcLen);
-                                           ^
-```
-
-(where only the second line contains `warning:`) into what looks like one
-`[WARNING]` and several `[ERROR]`s.
-
-If the compiler reports any actual errors, the build will fail.
-
 #### Capture the output of `mvn -X`
 
 The `-X` option will add a lot of information on the details of Maven's
@@ -259,3 +235,11 @@ On the first run, Maven will produce a lot of output while downloading all
 of the dependencies needed to complete the build. It is better, if the build
 fails, to simply run Maven again and capture the output of that run, which
 will not include all of the downloading activity.
+
+As an alternative, the flood of messages reflecting successful dependency
+downloads in a first run can be suppressed by adding this option on the `mvn`
+command line:
+
+```
+-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
+```

src/site/markdown/build/buildmsvc.md

@@ -211,26 +211,5 @@ dependency when [building your own projects that _use_ PL/Java][jproj].
 
 ### Troubleshooting the build
 
-If something fails, two tricks may be helpful. The C compilation may produce
-a lot of nuisance warnings, because the Maven plugin driving it enables many
-types of warning that would be impractical to fix. With many warnings it may
-be difficult to pick out messages that matter.
-
-If the link step of the build reports that the symbol `rint` is undefined you
-are probably using an older version of Visual Studio (2010) with a newer version
-of Postgresql (9.4). This symbol is defined in Visual Studio 2013 and later and
-the Postgresql 9.4 headers lack the appropriate conditional options for the
-older compilers. You will need to use a newer version of Visual Studio.
-
-On a machine with many cores, messages from several compilation threads may be
-intermingled in the output so that related messages are hard to identify.
-The option `-Dnar.cores=1` will force the messages into a sequential order
-(and has little effect on the speed of a PL/Java build).
-
-The `-X` option will add a lot of information on the details of Maven's
-build activities.
-
-    mvn  -X  -Dnar.cores=1  clean  install
-
-There is a more comprehensive "troubleshooting the build" section
+There is an extensive "troubleshooting the build" section
 on the [main build page][mbp].

src/site/markdown/build/package.md

@@ -25,13 +25,6 @@ When building a package, you are
 encouraged to set the default `pljava.libjvm_location` to the library of a
 JRE version that is expected to be present on your platform.
 
-**Note:** when building on Windows, the `-Dpljava.libjvmdefault` option is
-likely to produce a failed build or the wrong stored value for the library
-path. A fix for this option on Windows is unlikely (see [issue 190][bug190]);
-if preparing a package for Windows, it will be simplest to use a patch that
-changes the definition of `PLJAVA_LIBJVMDEFAULT` in
-`pljava-so/src/main/c/Backend.c`.
-
 [locatejvm]: ../install/locatejvm.html
 [bug190]: https://github.com/tada/pljava/issues/190
 
@@ -139,7 +132,7 @@ the package.
 
 `-Dpljava.libjvmdefault=`_path/to/jvm-shared-object_
 : As suggested earlier, please use this option to build a useful default
-into PL/Java for the `pljava.libjvm_location` PostgreSQL variable, users
+into PL/Java for the `pljava.libjvm_location` PostgreSQL variable, so users
 of your package will not need to set that variable before
 `CREATE EXTENSION pljava` works.
 
@@ -189,8 +182,11 @@ those needed to support `ALTER EXTENSION UPGRADE`.
 
 It also contains the `pljava-api` jar, needed for developing Java code to use
 in a database with PL/Java, and the `pljava-examples` jar. As discussed above,
-these may be omitted from a base package and supplied separately, if packaging
-guidelines require.
+the examples jar may be omitted from a base package and supplied separately,
+if packaging guidelines require, and the API jar may be included also in a
+`-devel` package that installs it in a standard Java-library location. (However,
+the API jar cannot be omitted from the base package; it is needed at runtime, in
+the `SHAREDIR/pljava` location where the extension expects it.)
 
 The self-extracting jar consults `pg_config` at the time of extraction to
 determine where the files should be installed.
@@ -226,9 +222,10 @@ will have on the target system.
 
 In addition to the files named in the self-extractor's output, additional
 files could be included in the package (if guidelines require the README
-or COPYRIGHT, for example). As discussed above, the `pljava-api` jar could
-be filtered from the list if it will be delivered in a separate `-devel`
-package, and the same could be done for `pljava-examples`.
+or COPYRIGHT, for example). As discussed above, the `pljava-examples` jar could
+be filtered from the list if it will be delivered in a separate
+package, and the `pljava-api` jar could be additionally delivered in a separate
+`-devel` package (but must not be excluded from the base package).
 
 [install]: ../install/install.html