http://defect.opensolaris.org/bz/show_bug.cgi?id=19201
Summary: OpenGrok shell script should reprocess configuration
file not use it directly
Classification: Development
Product: opengrok
Version: unspecified
Platform: ANY/Generic
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: misc
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
After bug 19175 was fixed the variables from configuration file given by the
OPENGROK_CONFIGURATION environment variable passed to OpenGrok shell script are
directly read-in by the script.
On one hand this is good since it allows users to modify various internal
variables but on the other hand it forces the users to use internal variables
which can change from release to release.
For instance, in order to enable JavaDB the supported way is to set the
OPENGROK_DERBY environment variable to non-empty string. But, when
OPENGROK_CONFIGURATION is used to supply all configuration to OpenGrok shell
script, one has to set the internal variable DERBY_HISTORY_CACHE to "-D" in the
configuration file.
Ideally, the script should set the defaults in the
DefaultInstanceConfiguration() and then read the OPENGROK_CONFIGURATION file in
and do the same. That way, the users will be able to consistently use only the
public environment variables of the OpenGrok script both on command line and in
the configuration file as well.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
opengrok-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opengrok-dev
