a) ready for qa workspace jaxpapi (issue 58308) moves OOo from using the sun specific sun.whatever api of “parser.jar” in favour of the standard jaxp api. As xercesImpl.jar and xml-apis.jar are available already in the xalan module, current references to “jaxp.jar” and “parser.jar” for jdk’s which don’t provide a jaxp implementation can be replaced with “xml-apis.jar” and “xercesImpl.jar” references. This allows OOo to be built without requiring these sun jars, which avoids the need for using non fully free jars at build time, and shrinks the source tree a smidgen.
b) planned workspace systemjava (issue 52974) depends on jaxpapi and should allow the use of pre-built system jars in place of hsqldb, beanshell and the xalan module contents. With the usual advantage of smaller build times and installation size and spreading distribution OOo support pain across a few more unsuspecting victims. Depends on being able to conditionalize the Ooo classpath profile.
c) planned workspace targedaot (issue 54692 depends on systemjava and jaxpapi and will enable using gcj’s ahead-of-time to native binary compilation mode in a less scatter gun approach i.e. only aot compile at build-time the java code itself required to build OOo, i.e. HelpLinker and FCFGMerge and their dependacies. Shrinking gcj users’ build times.