For docbook-xsl builds, feed xjparse the -EO and -w switches.
-E0
suppresses the "Parse succeeded... with no errors and no warnings"
messages that xjparse (actually, the XML Commons resolver)
otherwise emits.
-w
cause xjparse/resolver to only do a well-formedness check,
instead of trying to do validation; the reason for adding this
is that xjparse gets run against what are now doctype-less,
namespaced DocBook instances (after recent changes to the
build) and fails to validate those (because they don't have a
doctype)
What we really need to do long-term is replace xjparse with a
better, RELAXNG-aware validation mechanism, so that we can have
the build properly validate stuff that it should be checking.
That maybe amounts to making an "xslt" wrapper tool that either
calls jing or rnv (depending on what the builder wants to use).
But for now we'll need to tolerate that fact that xjparse isn't
doing anything more for us than just simply WF checking...