Documentation generation failure

[martindholmes]

We're trying to use Oxygen's stylesheetDocumentation.sh script to generate documentation, and on some machines (but not others), we're getting this error:

Code: Select all

Script file for generating XSL Stylesheet documentation

using oXygen XML Editor stylesheet documentation generator.

Exception in thread "main" java.lang.ExceptionInInitializerError

	at ro.sync.xsl.documentation.XSLStylesheetDocumentationGenerator.main(Unknown Source)

Caused by: java.lang.RuntimeException: The preferences directory: /root/.com.oxygenxml

cannot be accessed !/n Please check the read/write access on that folder and its ancestors !

	at ro.sync.exml.options.gc.n(Unknown Source)

	at ro.sync.exml.options.Options.r(Unknown Source)

	at ro.sync.exml.options.gc.q(Unknown Source)

	at ro.sync.exml.options.Options.<init>(Unknown Source)

	at ro.sync.exml.options.Options.<init>(Unknown Source)

	at ro.sync.exml.options.Options.z(Unknown Source)

	at ro.sync.exml.options.Options.getInstance(Unknown Source)

	at ro.sync.exml.r.e(Unknown Source)

	at ro.sync.exml.l.g.<clinit>(Unknown Source)

	... 1 more

Documentation generation did not succeed, return code 1

Why is oXygen trying to read/write to /root/ anything (it's running as a regular user), and what is it trying to access? Do you have any idea how we can avoid this?

[adrian]

Hi,

What version of Oxygen and what distribution (.sh, .tar.gz) are you using?

Oxygen tries to store its options in <user-home>/.com.oxygenxml.
This error could happen if Java somehow detects the user home of the current user as "/root", even though it's a regular user with a normal user home (/home/<username>).
You should check the environment of those users/machines.

There is a way to force the user home in the Java launchers, but this shouldn't be necessary if the environment is "clean".
Check if the HOME environment variable points to the correct location (printenv|grep HOME). If it does, you can use the argument "-Duser.home=${HOME}" (including the quotes) for the Java call from the scripts.
For the stylesheetDocumentation.sh you can add this just after the -Djava.awt.headless=true argument.

Regards,
Adrian